This is the mail archive of the
mailing list for the GCC project.
Re: Trouble with building multilib GCC (MinGW)
- From: niXman <i dot nixman at gmail dot com>
- To: gcc-help at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Sun, 11 Mar 2012 19:28:43 +0400
- Subject: Re: Trouble with building multilib GCC (MinGW)
- References: <CAMPTgK3+22Oj6tODhqdDvic=dr7xeT5Wumn4Vk5kTw2ZeVGcaA@mail.gmail.com> <email@example.com> <CAMPTgK0ec1EcuQiWQqVCJsocz-b_X1AEtbnD7Xn+irUvBRYhRA@mail.gmail.com> <CAMPTgK1uGHSsHUGwe_0EQa=C4KCkYJUM5v0yV+UzKivp-t5Hfirstname.lastname@example.org>
> 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?