public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10248: including system headers makes g++ barf Date: Fri, 28 Mar 2003 13:16:00 -0000 [thread overview] Message-ID: <20030328115601.10309.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10248; it has been noted by GNATS. From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> 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
next reply other threads:[~2003-03-28 11:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-28 13:16 Rainer Orth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-30 22:36 ehrhardt 2003-03-27 21:19 jhs
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=20030328115601.10309.qmail@sources.redhat.com \ --to=ro@techfak.uni-bielefeld.de \ --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).