From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10338 invoked by alias); 28 Mar 2003 11:56:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 10310 invoked by uid 71); 28 Mar 2003 11:56:01 -0000 Date: Fri, 28 Mar 2003 13:16:00 -0000 Message-ID: <20030328115601.10309.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Rainer Orth Subject: Re: c++/10248: including system headers makes g++ barf Reply-To: Rainer Orth X-SW-Source: 2003-03/txt/msg01995.txt.bz2 List-Id: The following reply was made to PR c++/10248; it has been noted by GNATS. From: Rainer Orth To: jhs@ocf.berkeley.edu Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/10248: including system headers makes g++ barf Date: 28 Mar 2003 12:46:43 +0100 jhs@ocf.berkeley.edu writes: > SunOS mustard 5.8 Generic_108528-15 sun4u sparc SUNW,UltraAX-i2 > >Description: > Including /usr/include/sys/stat.h causes my compile to fail. From what I can see, there is no reason this should be happening, and it works correctly on gcc 2.95.2 > > scott@mustard:~> gcc -v > Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/3.2.2/specs > Configured with: ../configure --srcdir=/usr/local/src/gnu/gcc-3.2.2/H-sun4-sunos5/.. --infodir=/usr/local/lib/info --with-gxx-include-dir=$(libsubdir)/g++-include --bindir=/usr/local/lang/gcc-3.2.2/bin > Thread model: posix > gcc version 3.2.2 > scott@mustard:~> g++ -v > Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.5.1/default/specs > gcc version 2.95.2 19991024 (release) You generally need to build gcc on the OS version it is intended to run on (Solaris 8 in this case). Since the fixincludes step of the build creates modified versions of some system headers and places them in a private include directory, you may wind up mixing unmodified new (Solaris 8) and modified old (Solaris 2.5.1 and 2.6) headers in one compilation, leading to all sorts of problems. Thus I cannot reproduce your problem with gcc 3.2.3 built on Solaris 8 and running on the same release. Rainer