From: Joe Buck <jbuck@synopsys.COM>
To: dje@watson.ibm.com (David Edelsohn)
Cc: chip.cuntz@earthling.net (Chip Cuntz), gcc@gcc.gnu.org
Subject: Re: Problem with <cstdio> and AIX 4.3.3
Date: Wed, 12 Dec 2001 15:51:00 -0000 [thread overview]
Message-ID: <200112122248.OAA12152@atrus.synopsys.com> (raw)
In-Reply-To: <200112122149.QAA24726@makai.watson.ibm.com> from "David Edelsohn" at Dec 12, 2001 04:49:56 PM
> >>>>> "Chip Cuntz" writes:
>
> Chip> g++ -c -I/usr/include -I../include -D__AIX__ -D__UNIX__ com_bmf.c
David Edelsohn writes:
> I just noticed something suspicious about your commandline: why
> are you explicitly adding -I/usr/include? The compiler implicitly
> searches that directory already. Your adding it to the commandline is
> altering the search order, probably causing GCC to find a different
> version of some header file than its own, internal version.
David's objection is not strong enough. For C++, any attempt to put
-I/usr/include on the command line, and then to include standard headers,
is likely to fail, unless your OS populates /usr/include only with ISO C++
compliant headers designed to work with g++. This pretty much means that
if you do this on any proprietary operating system, as well as most free
ones, it will fail.
prev parent reply other threads:[~2001-12-12 22:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 7:52 Build status page:Succes and failures Gcc k6 testing account
2001-12-07 9:40 ` Joe Buck
2001-12-12 10:35 ` Janis Johnson
2001-12-13 12:29 ` Gerald Pfeifer
2001-12-13 13:15 ` Janis Johnson
2001-12-13 16:54 ` Joe Buck
2001-12-13 17:38 ` Janis Johnson
2001-12-15 10:43 ` John Marshall
2001-12-17 9:08 ` Janis Johnson
2001-12-12 11:59 ` Problem with <cstdio> and AIX 4.3.3 Chip Cuntz
2001-12-12 12:20 ` David Edelsohn
2001-12-12 14:48 ` David Edelsohn
2001-12-12 15:51 ` Joe Buck [this message]
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=200112122248.OAA12152@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=chip.cuntz@earthling.net \
--cc=dje@watson.ibm.com \
--cc=gcc@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).