public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/3561: declaration of '__fmt' shadows previous local in ostream.tcc:490 Date: Fri, 06 Jul 2001 12:16:00 -0000 [thread overview] Message-ID: <20010706191602.29211.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/3561; it has been noted by GNATS. From: Phil Edwards <pedwards@disaster.jaj.com> To: Mathieu Olivier <molivier@microids.com> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: libstdc++/3561: declaration of '__fmt' shadows previous local in ostream.tcc:490 Date: Fri, 6 Jul 2001 15:16:23 -0400 On Fri, Jul 06, 2001 at 12:58:09PM +0200, Mathieu Olivier wrote: > > > >How-To-Repeat: > > > Just try to use ostream with -Wshadow > > > > Nope, doesn't happen. I do see the warning (along with a few others) if > > I use "-Wshadow -Wsystem-headers", but since <ostream> is a system header, > > warnings are suppressed by default. You must specifically request them. > > > Really ? I mean, I even tried with just "-Wshadow -Wno-system-headers" > (no -Wall, or any other -W*) and the warning appears anyhow. :( Ah. Figured it out. I missed this part of your original bug report: configured with: ../src/configure [...] --prefix=/usr Don't configure with --prefix=/usr unless you're a system vendor setting up a distribution. It severely confuses GCC's idea of which headers are system headers and which headers are yours. In this case, the C++ library headers (normally "system") are being detected as yours. Phil -- Would I had phrases that are not known, utterances that are strange, in new language that has not been used, free from repetition, not an utterance which has grown stale, which men of old have spoken. - anonymous Egyptian scribe, c.1700 BC
next reply other threads:[~2001-07-06 12:16 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-06 12:16 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-28 12:57 ljrittle 2001-07-11 13:46 Phil Edwards 2001-07-09 1:56 Mathieu Olivier 2001-07-05 14:36 Phil Edwards 2001-07-05 14:06 Phil Edwards 2001-07-04 8:56 molivier
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=20010706191602.29211.qmail@sourceware.cygnus.com \ --to=pedwards@disaster.jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).