public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jhs@ocf.berkeley.edu To: gcc-gnats@gcc.gnu.org Subject: c++/10248: including system headers makes g++ barf Date: Thu, 27 Mar 2003 21:19:00 -0000 [thread overview] Message-ID: <20030327210554.30413.qmail@sources.redhat.com> (raw) >Number: 10248 >Category: c++ >Synopsis: including system headers makes g++ barf >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu Mar 27 21:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: jhs@ocf.berkeley.edu >Release: gcc 3.2.2 >Organization: >Environment: 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) scott@mustard:~> gcc test.cc In file included from test.cc:1: /usr/include/sys/stat.h:258: 'blksize_t' is used as a type, but is not defined as a type. /usr/include/sys/stat.h:318: 'blksize_t' is used as a type, but is not defined as a type. scott@mustard:~> g++ test.cc scott@mustard:~> ./a.out hello >How-To-Repeat: #include <sys/stat.h> #include <stdio.h> int main() { printf("hello\n"); } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-27 21:06 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-27 21:19 jhs [this message] 2003-03-28 13:16 Rainer Orth 2003-03-30 22:36 ehrhardt
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=20030327210554.30413.qmail@sources.redhat.com \ --to=jhs@ocf.berkeley.edu \ --cc=gcc-gnats@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).