public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Phillips <msp@nortelnetworks.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7009: please provide command line option to turn off new include warnings
Date: Wed, 10 Jul 2002 09:56:00 -0000 [thread overview]
Message-ID: <20020710165600.10454.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/7009; it has been noted by GNATS.
From: Mark Phillips <msp@nortelnetworks.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, Hugues.Talbot@cmis.CSIRO.AU,
gcc-bugs@gcc.gnu.org
Cc:
Subject: Re: c++/7009: please provide command line option to turn off new
include warnings
Date: Wed, 10 Jul 2002 17:50:58 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7009
The new warnings also stop gcc 3.1itself from building...
In my case gcc gettext and libiconv are all installed in the same
directory, but the existing compiler does not pickup that include/lib dir.
If I use --with-libiconv-prefix=xxx it almost works except, but libjava
fails because its configure script thinks loads of things are missing
because the tests fail when they see the unexpected warning:-
cc1plus: warning: changing search order for system directory "/xxx"
cc1plus: warning: as it has already been specified as a non-system
directory
A similar problem also effects several other packages.
The new deprecated C++ library warnings also break the configuration of
some packages (though that can be fixed with a command line flag).
Cheers
Mark
next reply other threads:[~2002-07-10 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 9:56 Mark Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-14 14:44 nathan
2002-06-12 23:26 Hugues Talbot
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=20020710165600.10454.qmail@sources.redhat.com \
--to=msp@nortelnetworks.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: 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).