This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/20366] AIX g++ -D_LARGE_FILES fails to compile #include <iostream>
- From: "tcoleman at autowares dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Dec 2007 20:18:11 -0000
- Subject: [Bug target/20366] AIX g++ -D_LARGE_FILES fails to compile #include <iostream>
- References: <bug-20366-10214@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #14 from tcoleman at autowares dot com 2007-12-22 20:18 -------
(In reply to comment #12)
I don't see it as so much a matter of "focus".
A lot of applications test for _LARGE_FILES in the C library and will set it as
a configuration option if supported. As far as straight C goes, there's no
problem with gcc on AIX.
But if _LARGE_FILES is set, the fact that g++ can't compile C++ applications
using cstdio on AIX is a source of both frustration and annoyance.
Does G++ really have to be either one way or the other? Can't it also include
conditional code to check for _LARGE_FILES? Maybe I'm missing something here.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20366