---------- Forwarded message ---------- From: niXman <i.nixman@xxxxxxxxx> Date: 2012/3/10 Subject: Re: Trouble with building multilib GCC (MinGW) To: Ian Lance Taylor <iant@xxxxxxxxxx> 2012/3/10 Ian Lance Taylor <iant@xxxxxxxxxx>: > niXman <i.nixman@xxxxxxxxx> writes: > >> ping? > > When you ping a message, please include the context in the ping. > Otherwise we have to look it up. And since we are all volunteers, > requiring us to go back and look up the context makes it that much less > likely that you will get any sort of answer. Thanks. Thank's for your answer. I thought that copying the subject isn't a good idea ... The next time I will copy it. > > As far as I can tell from your original note, your build failed because > you do not have a 64-bit version of the library -lkernel32. That is not > a gcc library. I assume it is a Windows library. I don't know if you > are missing a 64-bit version of the library, or if the bug is that you > should not be linking against -lkernel32 for a 64-bit build. E.g., > perhaps there is a -lkernel64 on Windows, I don't know. I have built both versions of CRT for 32 and 64 bit. 32bit CRT in <prefix>/<target>/lib path, and 64bit in <prefix>/<target>/lib64 If you see logfile: http://pastebin.com/KiGHVgVQ then you can see that for linking 32bit and 64bit libgcc_s_sjlj-1.dll are used 32bit CRT. If in Makefile for 64bit version I replace <prefix>/<target>/lib with <prefix>/<target>/lib64 - linking is successfully. I.e. the problem is that wrong Makefiles are created. I want to understand why? > > You can probably get a better answer on a mingw or cygwin mailing list, > as that is where you will find people who understand the Windows > environment. There I began the discussion. But it seems like all ideas have ended: http://sourceforge.net/mailarchive/forum.php?thread_name=CAMPTgK2xXJuFumO7W9BWXdfooCd6Y1WXA%3D6NhH5HvwPvyPmuuw%40mail.gmail.com&forum_name=mingw-w64-public > > Ian -- Regards, niXman
