From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-42739-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 16071 invoked by alias); 12 Dec 2001 22:48:23 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 16050 invoked from network); 12 Dec 2001 22:48:23 -0000
Received: from unknown (HELO boden.synopsys.com) (204.176.20.19)
  by sources.redhat.com with SMTP; 12 Dec 2001 22:48:23 -0000
Received: from maiden.synopsys.com (maiden.synopsys.com [146.225.100.170])
	by boden.synopsys.com (Postfix) with ESMTP
	id 09C0FDA5D; Wed, 12 Dec 2001 14:48:22 -0800 (PST)
Received: from atrus.synopsys.com (localhost [127.0.0.1])
	by maiden.synopsys.com (8.9.1/8.9.1) with ESMTP id OAA19625;
	Wed, 12 Dec 2001 14:48:50 -0800 (PST)
From: Joe Buck <jbuck@synopsys.COM>
Received: (from jbuck@localhost)
	by atrus.synopsys.com (8.9.3+Sun/8.9.1) id OAA12152;
	Wed, 12 Dec 2001 14:48:21 -0800 (PST)
Message-Id: <200112122248.OAA12152@atrus.synopsys.com>
Subject: Re: Problem with <cstdio> and AIX 4.3.3
To: dje@watson.ibm.com (David Edelsohn)
Date: Wed, 12 Dec 2001 15:51:00 -0000
Cc: chip.cuntz@earthling.net (Chip Cuntz), gcc@gcc.gnu.org
In-Reply-To: <200112122149.QAA24726@makai.watson.ibm.com> from "David Edelsohn" at Dec 12, 2001 04:49:56 PM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-SW-Source: 2001-12/txt/msg00675.txt.bz2


> >>>>> "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.