Subject: Re: bug#48993: why error "unable to infer tagged configuration"?

From: Ileana Dumitrescu <[email-masked]>
Date: Wed, 8 Jan 2025 16:26:50 +0200

On 07/01/2025 23:21, Bruno Haible wrote:
...
> What I did (and this worked) was to replace the command
> 
>    /bin/sh ../libtool --mode=compile ml64 -c -nologo avcall-x86_64.asm
> 
> with the sequence of commands
> 
>    ml64 -c -nologo avcall-x86_64.asm
>    mkdir -p .libs; cp avcall-x86_64.@OBJEXT@ .libs/avcall-x86_64.@OBJEXT@
>    sed -e 's/avcall-libapi/avcall-x86_64/g' < avcall-libapi.lo > avcall-x86_64.lo
> 
> The first line simply invokes ml64 with the given arguments.
> The second line creates a copy of the .obj file under .libs/, like libtool
> does for supported compilers.
> The third line is a hack: it creates a .lo file, like libtool does for
> supported compilers.

Thank you for the commands and the explanation. :)

> Would it be possible to add support for ml64 to libtool, along these lines?

It is definitely possible, but it may be some time before I have an
implementation for it.

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354