public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "patrick133t at yahoo dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13682] Compile error with cstdio: fgetpos not declared on AIX Date: Tue, 03 Jun 2008 18:20:00 -0000 [thread overview] Message-ID: <20080603181952.9538.qmail@sourceware.org> (raw) In-Reply-To: <bug-13682-7634@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from patrick133t at yahoo dot com 2008-06-03 18:19 ------- I see this on AIX 5.3 also. I tracked it down by creating a simple program that just does a #include <string> and then saw that it worked when compiled as: g++ -c -o bar.o bar.cc However, it fails to compile when I do g++ -c -D_LARGE_FILES -o bar.o bar.cc I then grepped all the files that get included in the preprocessed output and found only these two reference _LARGE_FILES: /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.1.0.0/3.3.2/include/stdio.h /opt/freeware/lib/gcc-lib/powerpc-ibm-aix5.1.0.0/3.3.2/include/sys/types.h The problem appears to be that stdio.h makes the following definitions that then get #undef'ed in cstdio: #define fseeko fseeko64 #define ftello ftello64 #define fgetpos fgetpos64 #define fsetpos fsetpos64 #define fopen fopen64 #define freopen freopen64 Because of these defitions, the prototypes in the preprocessed output have a 64 on the end but the using ::fsetpos do not have them, and we get the error. I really think this is GCC's problem and not caused by AIX headers. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13682
next parent reply other threads:[~2008-06-03 18:20 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-13682-7634@http.gcc.gnu.org/bugzilla/> 2008-06-03 18:20 ` patrick133t at yahoo dot com [this message] 2009-08-20 7:31 ` oliver at FreeBSD dot org 2010-05-17 20:06 ` pedzsan at gmail dot com 2004-01-14 15:54 [Bug c++/13682] New: " richard_wheeler at cinfin dot com 2004-01-14 15:56 ` [Bug c++/13682] " richard_wheeler at cinfin dot com 2004-01-14 17:43 ` pinskia at gcc dot gnu dot org 2004-01-14 19:22 ` richard_wheeler at cinfin dot com 2004-01-14 19:26 ` richard_wheeler at cinfin dot com 2004-01-14 19:30 ` pinskia at gcc dot gnu dot org 2004-01-14 19:41 ` richard_wheeler at cinfin dot com
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=20080603181952.9538.qmail@sourceware.org \ --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).