2012/3/16 niXman <[email protected]>: > 2012/3/16 Kai Tietz <[email protected]>: >> 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 > > Done. > >> >> --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 > > Done. > >> >> 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. > > If I am in Windows, do I need to create symlink twice? The first time > after the mingw-w64-headers installing, and the second after > mingw-w64-crt installing? > > Now I have: > When linking libgcc_s_sjlj-1.dll 32bit: http://pastebin.com/U0jAV34G > When linking libgcc_s_sjlj-1.dll 64bit: http://pastebin.com/wSeUuWxn > > And one more question... After installing gcc-core (make all-gcc) and > adding in the PATH, I build winpthreads 32 and 64 bit. Is this wright? > I'm asking, because wiki doesn't say a word about this. >
Ping? -- Regards, niXman ------------------------------------------------------------------------------ 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
