-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 3/10/2011 23:18, K Shen wrote: > Hi, > > I posted messages earlier about the problem I had with a binary MinGW-w64 > (for cross-compiling to Win64 on Linux), I assume this binary is built from > the trunk branch of MinGW, and Kai Tietz suggested that one way round this is > to fallback to 1.0 branch-math. > > As I wasn't able to work round the problem with the binary I had, I decided > to try the branch 1.0 approach. Am I correct in assuming this means release > 1.0 of MinGW-w64? Firstly, is this correct -- release 1.0 will have the older > math routines? > > I downloaded a binary for (32 bit) Linux of the release 1.0 MinGW-w64 from > your ftp site, but was unable to run the gcc cross-compiler, because it needs > a newer glibc than what is on my Linux system.[My previous binary was > downloaded from http://www.drangon.org/mingw, and I guess they linked against > an older version of glibc that works on my Linux) > > So it seems I need to compile MinGW-w64 myself. I downloaded: > > http://sourceforge.net/projects/mingw-w64/files/Toolchain%20sources/Automated%20Builds/mingw-w64-1.0-src-_20110307.tar.bz2 > > > but I cannot figure out how to build this. There appears to be both gcc and > binutil sources in this package, as well as the release branch of mingw, but > there is no configure file in the mingw directory, nor a top-level configure > at the toplevel directory. > > I looked at the instructions in the FAQ (How do I compile multilib > toolchain), but I am not sure which configure file it is referring to in the > various steps, I assume it is the configure in the component I am building, > e.g. binutil's for binutil, but there is no configure in the mingw directory, > which I assume is the 'runtime' component? >
Hi, read the makebuildroot.mk and makebuildroot-test.mk file to see how its done. In fact, you could use it to automatically download and build the toolchain for you. > In > http://sourceforge.net/apps/trac/mingw-w64/wiki/Cross%20Win32%20and%20Win64%20compiler > > it mentions CRT as runtime -- does this mean I need to run the configure in > mingw/mingw-crt? > yes. > Another question: I assume sysroot is the path I want to install the > toolchain to? > No. They are where the compiler finds its headers and libraries. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) iEYEARECAAYFAk148r4ACgkQp56AKe10wHfdTACfc9b6fTo3ZWWXmIMxZhk/YQzU 2soAoIJ298D2li6Wzx6H4hR186JF8a7N =t3tf -----END PGP SIGNATURE-----
0xED74C077.asc
Description: application/pgp-keys
------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
