Re: Trouble with building multilib GCC (MinGW)

[Ian Lance Taylor <iant@xxxxxxxxxx>]

niXman <i.nixman@xxxxxxxxx> writes:

> 2012/3/12 Ian Lance Taylor <iant@xxxxxxxxxx>:
>>
>> To be honest I don't see that in the pastebin.  The use of -m64 should
>> cause the multilib support to kick in, and in particular should cause
>> the gcc driver to add /../lib64 to the end of the -L paths.  I guess
>> that is not happening, but I can't see it from the log.
>
> In the fourth line uccurs linking 64bit libgcc_s_sjlj-1.dll. In this
> you can see by searching for 'm64'. Also, in the fourth line you can
> see the path used to search for 64bit CRT, and make sure that the path
> is used only for 32bit CRT.

When I look at the fourth line of the pastebin link you posted earlier
(http://pastebin.com/KiGHVgVQ) I see an invocation of xgcc.  I can not
see the path used to search for the crt file in that line.  The -B and
-L options passed to xgcc are not the final search path.  The final
search path is computed by the gcc driver by applying multilib
transformations to the -B and -L options.  In order to see the actual
search path, you will need to run that exact command with the -v option.


>> gcc --print-multi-lib
> $ i686-w64-mingw32-gcc --print-multi-lib
> .;
> 64;@m64
>
>
>> gcc --print-multi-directory
> $ i686-w64-mingw32-gcc --print-multi-directory
> .
>
>
>> gcc --print-multi-directory -m32
> $ i686-w64-mingw32-gcc --print-multi-directory -m32
> .
>
>
>> gcc --print-multi-directory -m64
> $ i686-w64-mingw32-gcc --print-multi-directory -m64
> 64

Thanks.  That all looks fine but I now realize that I need something
else.  The output of:

gcc --print-multi-os-directory
gcc --print-multi-os-directory -m32
gcc --print-multi-os-directory -m64

Ian