Yes, you are actual build a cross-compiler from i686-pc-mingw32 to
i686-w64-mingw32. It is a cross, as triplets are different!
2. building binutils:
--target=i686-w64-mingw32
--enable-targets=x86_64-w64-mingw32,i686-w64-mingw32
^^ just a nit but might be of interest use here instead
--enable-targets=i686-w64-mingw32,x86_64-w64-mingw32
--enable-multilib
--enable-64-bit-bfd
--prefix=$PREFIX
--with-sysroot=$PREFIX
--disable-nls
--enable-lto
--with-libiconv-prefix=$LIBS_DIR
3. building mingw-w64-headers:
--host=i686-w64-mingw32
--target=i686-w64-mingw32
^^^don't use here --target option
--prefix=$PREFIX
--with-sysroot=$PREFIX
--enable-sdk=all
--enable-secure-api
Here you should make sure that temporary the $PREFIX/mingw folder is a
link to $PREFIX/i686-w64-mingw32 folder. After building all you can
remove this link.
4. building gcc-c:
--target=i686-w64-mingw32
--enable-targets=all
--enable-multilib
--prefix=$PREFIX
--with-sysroot=$PREFIX
--enable-languages=c,c++,lto
5. building mingw-w64-crt:
--host=i686-w64-mingw32
--prefix=$PREFIX
--with-sysroot=$PREFIX
--enable-lib32
--enable-lib64
--enable-wildcard
6. building gcc-all:
make all
Regards,
Kai
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
