This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/12778] 3.4 1022 bootstrap failure building libstdc++-v3/src/basic_file.cc
- From: "paolo at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Oct 2003 12:01:48 -0000
- Subject: [Bug libstdc++/12778] 3.4 1022 bootstrap failure building libstdc++-v3/src/basic_file.cc
- References: <20031026100240.12778.rdbrown@mira.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12778
paolo at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
------- Additional Comments From paolo at gcc dot gnu dot org 2003-10-26 12:01 -------
Hi. We never define _LARGEFILE64_SOURCE or whatelse because the implicit
_GNU_SOURCE should suffice for glibc (other libc have to wait a bit...)
But the point is another: why the autoconf test succeeds and then the build
fails? This is really strange! What happens if you try to compile with your
gcc a small "C" program like:
cat autotest.c:
#include <unistd.h>
int main()
{
lseek64(1, 0, SEEK_CUR);
return 0;
}
???
And what if you do the same but as a C++ program, *.cc?
Thanks,
Paolo.