Hi xunxun,
2011/10/14 xunxun <[email protected]>
Before cross building gcc, you should rebuild mingw64 headers and install to
your prefix.
> --
> Best Regards,
> xunxun
>
> I have followed all the steps mentioned in the guide, including this one
of course. So the problem does not come from not having installed mingw64
headers, but rather from the fact that the new headers are not picked up. In
the search dir of my cross compiler, you would have noticed that I have:
.
../../../../src/mingw-w64-trunk-20110723/mingw-w64-crt
C:\s2e\s2e-toolchain\mingw64\x86_64-w64-mingw32\include
c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include
c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\lib/gcc/x86_64-w64-mingw32/4.7.0/include-fixed
C:/s2e/s2e-toolchain/home/aceg7283/toolchain_gcc_4.6/build/mingw64/target/x86_64-w64-mingw32/include
c:\s2e\s2e-toolchain\home\aceg7283\toolchain_gcc_4.6\build\mingw64\target\mingw/include
Why do I have the second one, which is the one messing up everything I
think.
--
Alexandre
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
