GNU bug report logs - #48993
why error "unable to infer tagged configuration"?

Previous Next

To reply to this bug, email your comments to 48993 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bruno Haible <bruno <at> clisp.org>
To: bug-libtool <at> gnu.org
Subject: why error "unable to infer tagged configuration"?
Date: Sun, 13 Jun 2021 04:26:39 +0200

Hi,

In a Makefile of mine, I want to use libtool to compile a .asm file with
the Microsoft assembler, for use in a libtool library:

  /bin/sh ../libtool --mode=compile ml64 -c -nologo avcall-x86_64.asm
  libtool: compile: unable to infer tagged configuration
  libtool:   error: specify a tag with '--tag'

The documentation [1] says:

  "libtool tries to automatically infer what tag to use from the compiler
   command being used to compile or link. If it can’t infer a tag, then it
   defaults to the configuration for the C language."

If it defaults to --tag=C, why does libtool report an error then?

       Bruno

[1] https://www.gnu.org/software/libtool/manual/html_node/Tags.html

Message #8 received at 48993 <at> debbugs.gnu.org (full text, mbox):

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 48993 <at> debbugs.gnu.org
Cc: Bruno Haible <bruno <at> clisp.org>
Subject: Re: bug#48993: why error "unable to infer tagged configuration"?
Date: Tue, 7 Jan 2025 21:39:55 +0200

[Message part 1 (text/plain, inline)]

Hi,

Thank you for your bug report.

I do not see that Libtool supports ml64, the Microsoft Macro Assembler.
The error you received is for not using the --tag option. Since there
are different configurations for the different tags, it is important to
specify the intended configuration. However, an unsupported compiler
could be used with a supported tag, which would lead to issues with
object and library creation. I will work on a fix for this bug, but this
commit [1] should help users understand tagging better.

Since ml64 is unsupported, I suggest recreating the file in C, and then,
the C compiler could be used to generate an assembly file to link within
a library. However, it would be better to add assembly compilation to
Libtool.

[1] 
https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=376411905b3f479b52c69a8a62f258b6ba62fc01

-- 
Ileana Dumitrescu

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

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Message #11 received at 48993 <at> debbugs.gnu.org (full text, mbox):

From: Bruno Haible <bruno <at> clisp.org>
To: 48993 <at> debbugs.gnu.org, Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
Subject: Re: bug#48993: why error "unable to infer tagged configuration"?
Date: Tue, 07 Jan 2025 22:21:03 +0100

Hi Ileana,

> I do not see that Libtool supports ml64, the Microsoft Macro Assembler.
> ... However, an unsupported compiler
> could be used with a supported tag, which would lead to issues with
> object and library creation.

I see. Thanks for explaining.

> Since ml64 is unsupported, I suggest recreating the file in C, and then,
> the C compiler could be used to generate an assembly file to link within
> a library.

That would likely be more complex and more effort than adding ml64 support
to libtool.

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.  

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

Bruno

Message #14 received at 48993 <at> debbugs.gnu.org (full text, mbox):

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 48993 <at> debbugs.gnu.org
Cc: Bruno Haible <bruno <at> clisp.org>
Subject: Re: bug#48993: why error "unable to infer tagged configuration"?
Date: Wed, 8 Jan 2025 16:26:50 +0200

[Message part 1 (text/plain, inline)]

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

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Message #17 received at 48993 <at> debbugs.gnu.org (full text, mbox):

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 48993 <at> debbugs.gnu.org
Cc: Bruno Haible <bruno <at> clisp.org>
Subject: Re: bug#48993: why error "unable to infer tagged configuration"?
Date: Fri, 22 Aug 2025 20:43:12 +0300

[Message part 1 (text/plain, inline)]

On 08/01/2025 16:26, Ileana Dumitrescu wrote:
> On 07/01/2025 23:21, Bruno Haible wrote:
>> 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.
> 

Some time has passed, and I finally have an implementation for ML64 :)

https://cgit.git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=41e81b7b969a373f2909695d62e328ab17dc4d9d

Please share any updates that should be made before it migrates to
the master branch in a few weeks hopefully.

-- 
Ileana Dumitrescu

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

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.