public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "psmith at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/48996] New: fixincl on Red Hat EL 5 breaks sys/stat.h fstat64() Date: Sat, 14 May 2011 06:47:00 -0000 [thread overview] Message-ID: <bug-48996-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48996 Summary: fixincl on Red Hat EL 5 breaks sys/stat.h fstat64() Product: gcc Version: 4.5.3 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: psmith@gnu.org Hi all. When I run fixincl from GCC 4.5.3 on my Red Hat EL 5 system, the resulting sys/stat.h will throw an error whenever I try to call fstat64() from my code. If I delete sys/stat.h from the include-fixed directory, so the original is used, then all is happy again. Before fixincl the code reads: extern int fstat64 (int __fd, struct stat64 *__buf) __THROW __nonnull ((2)); After fixincl it reads: #ifdef __GNUC_GNU_INLINE__ extern #endif __inline__ int fstat64 (int __fd, struct stat64 *__buf) __THROW __nonnull ((2)); and the compiler error I get is: include-fixed/sys/stat.h:255:16: error: inline function 'int fstat64(int, stat64*)' used but never defined where line 255 is the __inline__ line above. Checking with the preprocessor I see that __GNUC_GNU_INLINE__ is built-in defined to be 1.
next reply other threads:[~2011-05-14 2:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-14 6:47 psmith at gnu dot org [this message] 2011-05-16 11:28 ` [Bug c/48996] " rguenth at gcc dot gnu.org 2011-05-16 13:00 ` psmith at gnu dot org 2011-05-16 13:26 ` rguenth at gcc dot gnu.org 2011-05-16 15:29 ` psmith at gnu dot org 2011-05-16 16:22 ` psmith at gnu dot org 2015-03-17 6:49 ` mpolacek at gcc dot gnu.org 2015-03-18 19:35 ` psmith at gnu dot org
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=bug-48996-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).