On 3/6/2012 08:42, niXman wrote: > 2012/3/6 JonY <[email protected]>: >> On 3/6/2012 02:47, niXman wrote: >>> The same error on building crt: _libm_dummy.c:1:0: sorry, >>> unimplemented: 64-bit mode not compiled in >>> >>> That`s how I do it : >>> 1. binutils: >>> --host=i686-pc-mingw32 >>> --build=i686-pc-mingw32 >>> --enable-targets=x86_64-w64-mingw32,i686-pc-mingw32 >>> --enable-multilib >>> --prefix=$PREFIX >>> --with-sysroot=$PREFIX >>> >>> 3. set PATH: >>> export PATH=$PREFIX/bin:$PATH >>> >>> 4. gcc-c: >>> --host=i686-pc-mingw32 >>> --build=i686-pc-mingw32 >>> --target=i686-pc-mingw32 >>> --enable-targets=all >>> --enable-multilib >>> --prefix=$PREFIX >>> --with-sysroot=$PREFIX >>> >>> 5. crt: >>> --enable-lib32 >>> --enable-lib64 >>> --prefix=$PREFIX >>> --with-sysroot=$PREFIX >>> >>> What am I doing wrongly? >>> >>> Thanks. >> >> Your binutils and gcc --target, use w64 instead of pc, and use >> --enable-fully-dynamic-string if you want it compatible with mingw-w64 >> builds. > The error persists. When building crt/lib64: '_libm_dummy.c:1:0: > sorry, unimplemented: 64-bit mode not compiled in' > It is also unclear, why it is used i686-pc-mingw32-gcc, while > i686-w64-mingw32 must be used. In PATH it is available: > >> i686-pc-mingw32-gcc -DHAVE_CONFIG_H -I. >> -I../../mingw-src/mingw-w64-crt -m64 -pipe >> -std=gnu99 -Wall -Wextra -Wformat -Wstrict-aliasing >> -Wshadow -Wpacked -Winline -Wimplicit-function-declaration >> -Wmissing-noreturn -Wmissing-prototypes -O3 -pipe >> -fomit-frame-pointer -momit-leaf-frame-pointer >> -I/mingw-libs/include -MT lib64_libm_a-_libm_dummy.o >> -MD -MP -MF .deps/lib64_libm_a-_libm_dummy.Tpo >> -c -o lib64_libm_a-_libm_dummy.o `test -f '_libm_dummy.c' || >> echo '../../mingw-src/mingw-w64-crt/'`_libm_dummy.c > > Output of configure: >> checking build system type... i686-w64-mingw32 >> checking host system type... i686-w64-mingw32 >> checking for sysroot... no >> checking for a sed that does not truncate output... /bin/sed >> checking for gcc... i686-pc-mingw32-gcc
You don't have a i686-w64-mingw32-gcc at all, you have i686-pc-mingw32-gcc instead. I have already told you to rebuild with "w64". > > last line. > > configure flags: > --build=i686-w64-mingw32 > --prefix=$PREFIX > --enable-lib32 > --enable-lib64 > >> >> Please, learn to read the build scripts and docs before jumping in blindly. > > I have read wiki. I have built x86-x86_64 and x86_64-x86_64 succesfully. > But wiki contains very little information about building the multilib > compiler. > > And there is almost not a word about host/build/target. From what > options that depends, on what it influences, for what, why, and so > on... - Everyone just has to guess and learn someone's scripts... > Maybe for some it's obvious, but not for those who read wiki. > > Thanks. > Its not obvious because you ignored my advice. Seriously, slow down a bit, take some time to actually digest your reading.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
