Re: libtool woes

[Ozkan Sezer]

On 9/10/13, Peter Rosin <address@hidden> wrote:
> On 2013-09-10 15:00, Ozkan Sezer wrote:
>> On 9/10/13, Peter Rosin <address@hidden> wrote:
>>> On 2013-09-10 12:52, Ozkan Sezer wrote:
>>>> That effectively cripples libtool for cross-compilers. Can the behavior
>>>> be refined instead?  Can you contact Charles Wilson about this?
>>>
>>> He should be reading this list, if he has time...
>>>
>>> Anyway, does this work?
>>>
>>
>> No, it does not.  With this patch applied, I see
>> sys_lib_search_path_spec="/opt/W64_180676/lib/gcc "
>> ..  in the libtool --config output.
>
> Crap, I didn't do any final test and managed to exclude a couple
> of critical changes, and I did a couple of silly mistakes too. Sorry
> about that. Attached is what I should have sent the first time...
>

Thanks, this one makes it to work. ./libtool --config output now has:

sys_lib_search_path_spec="/opt/W64_180676/lib/gcc
/opt/W64_180676/x86_64-w64-mingw32/lib64 /opt/cross_win64/mingw/lib64
/opt/W64_180676/x86_64-w64-mingw32/lib /opt/cross_win64/mingw/lib "

which is suitable.

>> (Note that, this is not a multilib compiler: it targets only win64.)
>
> Even so, I believe that it outputs ../lib64 when you
> -print-multi-os-directory, right?
>

Well yeah, it does :)

Is it hard to implement a way of directly respecting --print-search-dirs
output of the compiler though?

--
O.S.