From: Michael Haubenwallner <michael.haubenwallner@salomon.at>
To: Jonathan Saxton <jsaxton@appsecinc.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 4.2.x large file support
Date: Thu, 08 May 2008 07:31:00 -0000 [thread overview]
Message-ID: <1210229946.417.3.camel@sapc154.salomon.at> (raw)
In-Reply-To: <001f01c8b075$43776720$351110ac@nycapt35k.com>
On Wed, 2008-05-07 at 15:05 -0400, Jonathan Saxton wrote:
> I think I have found a problem in the g++ header files concerning large file
> support. I have seen it on two different AIX machines, one running AIX 5.3
> and using gcc 4.1.2, the other running AIX 5.2 and using a slightly later
> version of gcc, namely 4.2.2.
>
> cstdio carefully #undefs all the routines in stdio.h and then issues a
> "using" directive for each. The problem is that when large file support is
> enabled, routines like fgetpos() have been remapped to the 64-bit
> equivalents, fgetpos64() in this example.
This is http://gcc.gnu.org/PR20366
HTH,
/haubi/
prev parent reply other threads:[~2008-05-08 6:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 14:27 GCC 4.3.0 configure failure: libgcc James Molloy
2008-05-06 23:25 ` Ralf Wildenhues
2008-05-07 8:16 ` James Molloy
2008-05-07 21:06 ` gcc 4.2.x large file support Jonathan Saxton
2008-05-08 7:31 ` Michael Haubenwallner [this message]
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=1210229946.417.3.camel@sapc154.salomon.at \
--to=michael.haubenwallner@salomon.at \
--cc=gcc-help@gcc.gnu.org \
--cc=jsaxton@appsecinc.com \
/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: link
Be 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).