public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/99172] Build failure with slibtool and vtv
Date: Wed, 24 Feb 2021 13:44:24 +0000 [thread overview]
Message-ID: <bug-99172-4-BjWTgocTFX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99172-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cmtice at google dot com,
| |egallager at gcc dot gnu.org
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to gcc-user from comment #2)
> > Briefly it explained that -lvtv comes from -fvtable-verify=std in a gcc spec
> > file and is propogated to Makefile.in by gcc/Makefile.def.
>
> The -fvtable-verify=std doesn't come from the spec file, it comes from using
> --enable-vtable-verify to configure gcc. That adds -fvtable-verify=std and
> the spec file turns that into -lvtv.
>
> I don't know why you want to use --enable-vtable-verify but it's not really
> maintained as far as I can see.
I thought Caroline Tice was maintaining it.
next prev parent reply other threads:[~2021-02-24 13:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 20:52 [Bug libstdc++/99172] New: " gcc-user at riseup dot net
2021-02-22 8:42 ` [Bug libstdc++/99172] " rguenth at gcc dot gnu.org
2021-02-22 15:16 ` gcc-user at riseup dot net
2021-02-22 15:35 ` redi at gcc dot gnu.org
2021-02-22 16:18 ` gcc-user at riseup dot net
2021-02-23 3:46 ` gcc-user at riseup dot net
2021-02-24 13:44 ` egallager at gcc dot gnu.org [this message]
2021-02-24 16:27 ` ctice at gcc dot gnu.org
2021-02-24 16:56 ` gcc-user at riseup dot net
2021-02-24 17:06 ` ctice at gcc dot gnu.org
2021-02-24 18:57 ` redi at gcc dot gnu.org
2021-03-11 5:03 ` ctice at gcc dot gnu.org
2021-03-11 13:33 ` redi at gcc dot gnu.org
2021-03-15 16:43 ` cvs-commit at gcc dot gnu.org
2021-03-15 22:01 ` gcc-user at riseup dot net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99172-4-BjWTgocTFX@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).