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

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

------- Comment #6 from ktietz at gcc dot gnu dot org  2009-04-12 19:49 -------
(In reply to comment #5)
> I see this bug in compiler driver is already known
> (http://sourceforge.net/forum/forum.php?thread_id=3091795&forum_id=723797), it
> works only with "-O0". I can't found report about this bug in database.. does
> it exists ?
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.

> > Well, on 4.4 branch there was a patch introducing the winsup link, which got necessary for building libstdc++. We solve this by setting up in gcc's source tree a symbolic link "winsup" pointing to the sysroot (prefix) directory.
> 
> 
> Symbolic link "winsup" to prefix directory with mingw-w64 runtime headers not
> works properly with current gcc 4.4.0 snapshot.. for correct build you must
> *temporary* remove file "stddef.h" from
> ${YOUR_PREFIX}/x86_64-pc-mingw32/include because it conflicts with same file in
> libstdc++ build directory.
> 

Hmm, I tested a native build with current 4.4 gcc and I had no issues about it.

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.
If you need further help you can join #mingw-w64 on irc.oftc.net.

Cheers,
Kai


-- 


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