[Bug target/39738] GCC cannot build itself for win64 platform

["ktietz at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #8 from ktietz at gcc dot gnu dot org  2009-04-13 08:34 -------
(In reply to comment #7)
> > Please make sure, that you have in your gcc source root directory the symbolic
> > link "winsup" pointing to your prefix directory. Secondly, make sure you have
> > the symbolic link "mingw" in your prefix directory, which has to point to
> > x86_64-pc-mingw32 directory.
> 
> I use Gentoo Linux x64 as build OS with system compiler gcc 4.3.3,
> configuration script arguments you can see in my first post. Both symbolic
> links were created.. existing stddef.h file in winsup/mingw/include causes
> error: 'NULL' was not declared in this scope during libstdc++ building (see my
> earlier post).
> 
> > Yes, there is already one. But this bug is work-a-round by a temporary hack in
> > our crt. So it shouldn't appear anymore.
> Alltimes use -O0 is not the solution.. temporary CRT hacks too. Where I can get
> more information about this bug ?
> 

Why using all time -O0? This bug you reference to is not related to your
bootstrap issue.
So, the only issue I see here are the following possible reasons (beside the
possibility of wrong symbolic links, which you have shown to setup properly).
Do you use for native toolchain an fresh initialized directory?
Which version of toolchain you are using (especially header-set)?
Do you use --prefix and --with-sysroot options?

You can try the following. Remove in your <prefix> directory the folder
lib/gcc/x86_64-pc-mingw32/4.4.0/ and remove in your gcc's build directory the
x86_64-pc-mingw32 folder. Then do a 'make'. This error can happen also, when
the sysroot headers are copied too late (after the 'make all-gcc', because
fixinclude get executed already here).

Cheers,
Kai


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738