This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/30915] [4.3 regression] bootstrap fails while building libstdc++-v3 on x86_64-pc-linux-gnu
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Mar 2007 23:09:49 -0000
- Subject: [Bug libstdc++/30915] [4.3 regression] bootstrap fails while building libstdc++-v3 on x86_64-pc-linux-gnu
- References: <bug-30915-7220@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #20 from pcarlini at suse dot de 2007-03-12 23:09 -------
(In reply to comment #19)
...
> this isn't enough even with building with this brand new
> gcc-4.3.0_alpha20070309.
> I'll repeat it with include of proper stdio.h, which looks in gentoo multilib
> like this
>
> jama gcc # cat /usr/include/stdio.h
Ok, thanks. But then, an important question is: which (empty? not including any
declaration of the expected facilities?!? What header is that?) stdio.h is
instead included at build time if you don't specify explicitely the path? You
should try to figure out that, whether on your system there are around (in the
build directory or elsewhere) stdio.h which in fact are not the correct one.
In order to do that, you could proceed as follows: go the build directory of
the library and invoke by hand the same line which is failing the build of
compatibility.cc, but running only the preprocessor, with -E. You save its
output, it should tell us what a heck of wrong stdio.h is included.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30915