public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com> To: dje@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/10390: [AIX 4.3.3] conflicting declarations in stdio.h Date: Sat, 26 Apr 2003 21:16:00 -0000 [thread overview] Message-ID: <20030426211600.30291.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10390; it has been noted by GNATS. From: David Edelsohn <dje@watson.ibm.com> To: Jens Rehsack <rehsack@liwing.de> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: target/10390: [AIX 4.3.3] conflicting declarations in stdio.h Date: Sat, 26 Apr 2003 17:15:01 -0400 >>>>> Jens Rehsack writes: Jens> I don't share your point of view, because defining both macros Jens> (_LARGE_FILES and _LARGE_FILE_API) causes the failure. Or is Jens> documentation existing (which I didn't found) where it's forbidden Jens> defining both? Yes, this is a bug, but this is not a *GCC* bug. GCC *does not* provide its own stdio.h. GCC "fixes" many system headers, including stdio.h. Possibly GCC should modify the logic of these macros, but the original stdio.h in AIX is the one with the conflicting declarations. One needs to look at the manual for use of the macros. Possibly the bug is the GNU sed configuration for choosing to define both macros. Yes, there is a bug, but GCC did not create the conflicting declarations, so GCC is not the source of the bug. Just because the error message lists the GCC installation directory in the path does not mean that GCC is responsible. David
next reply other threads:[~2003-04-26 21:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-26 21:16 David Edelsohn [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-26 6:46 Jens Rehsack 2003-04-25 20:17 dje
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=20030426211600.30291.qmail@sources.redhat.com \ --to=dje@watson.ibm.com \ --cc=dje@gcc.gnu.org \ --cc=gcc-prs@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).