GNU bug report logs -
#67539
GNU Automake 1.16.5 FAILS one test objc-megademo
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 67539 in the body.
You can then email your comments to 67539 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Wed, 29 Nov 2023 21:44:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Dennis Clarke <dclarke <at> blastwave.org>
:
New bug report received and forwarded. Copy sent to
bug-automake <at> gnu.org
.
(Wed, 29 Nov 2023 21:44:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Not a bad result .... just one bad test result and it looks to be
related to something weird with libtool :
/bin/bash ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I.
-D_LARGEFILE64_SOURCE -g -O2 -MT fooo.lo -MD -MP -MF .d
eps/fooo.Tpo -c -o fooo.lo fooo.m
libtool: compile: unable to infer tagged configuration
libtool: error: specify a tag with '--tag'
make[1]: *** [Makefile:661: fooo.lo] Error 1
make[1]: Leaving directory
'/opt/bw/build/automake-1.16.5_linux_pentium_G4500.002/t/objc-megademo.dir'
make: *** [Makefile:439: all] Error 2
I have attached the test-suite.log but really, this looks to be a fairly
decent result.
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
[automake-1.16.5_linux_pentium_G4500_test-suite.log.gz (application/gzip, attachment)]
Information forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Fri, 01 Dec 2023 02:47:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 67539 <at> debbugs.gnu.org (full text, mbox):
Hi Dennis,
libtool: compile: unable to infer tagged configuration
Thanks for the report.
As you surmise, apparently this needs to be reported to
libtool. (Although afaik libtool is currently unmaintained, so I don't
know when or if anything will get fixed.) At least, I have no idea what
to do about, or even work around, that error :(.
What is the os version + hardware? If it's easy for you to try the
automake development sources, that could be worth a try. Else hopefully
there will be a pretest+release soon. --best, karl.
Information forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Fri, 01 Dec 2023 03:46:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 67539 <at> debbugs.gnu.org (full text, mbox):
On 2023-11-30 21:46, Karl Berry wrote:
> Hi Dennis,
>
> libtool: compile: unable to infer tagged configuration
>
> Thanks for the report.
>
> As you surmise, apparently this needs to be reported to
> libtool. (Although afaik libtool is currently unmaintained, so I don't
> know when or if anything will get fixed.) At least, I have no idea what
> to do about, or even work around, that error :(.
This could still be (partially) an Automake issue, since the problem
appears partially related to how Automake is calling libtool from the
build rules (it is missing the --tag option), and I think those are
coming from Automake.
However it looks like there is no tag defined for Objective C[1]
(presumably it would be --tag=OBJC). Adding this option does appear to
make things "work" in the sense that libtool just complains about the
unknown tag but then proceeds to actually do stuff, rather than exiting
outright with a fatal error.
Interestingly the libtool manual also says "If [libtool] can't infer a
tag, then it defaults to the configuration for the C language", which is
clearly not the case (it seems what actually happens is that if libtool
can't infer a tag then it exits with a fatal error). So I wonder if
this is actually a regression in libtool.
[1] https://www.gnu.org/software/libtool/manual/libtool.html#Tags
Cheers,
Nick
Information forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Sat, 02 Dec 2023 21:44:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 67539 <at> debbugs.gnu.org (full text, mbox):
However it looks like there is no tag defined for Objective C[1]
(presumably it would be --tag=OBJC). Adding this option does appear
to make things "work" in the sense that libtool just complains about
the unknown tag but then proceeds to actually do stuff, rather than
exiting outright with a fatal error.
Thanks Nick.
Does libtool actually work (well enough) with Objective C, then? Apart
from the warning about the tag. I don't see it mentioned in the libtool
sources.
Anyway, I guess it's easy enough to add the tag, if that makes things
better. Why not, I guess? Patch below look right? (Plus maybe something
in the manual.)
BTW, I've been unable to install objc on my systems (Alma 8, Rocky 9)
since installing the gcc-objc + libobjc packages does not suffice.
The result is still:
gcc: error: foo.m: Objective-C compiler not installed on this system
I see some ideas about how to proceed on the net, but ... time.
From the lack of reports about this test failure (yours was the first,
Dennis, as far as I can recall), I surmise that hardly anyone (who cares
about automake anyway) has objc installed. --thanks, karl.
--- a/bin/automake.in
+++ b/bin/automake.in
@@ -739,6 +739,7 @@ register_language ('name' => 'objc',
'compiler' => 'OBJCCOMPILE',
'compile_flag' => '-c',
'output_flag' => '-o',
+ 'libtool_flag' => 'OBJC',
'lder' => 'OBJCLD',
'ld' => '$(OBJC)',
'pure' => 1,
@@ -757,6 +758,7 @@ register_language ('name' => 'objcxx',
'compiler' => 'OBJCXXCOMPILE',
'compile_flag' => '-c',
'output_flag' => '-o',
+ 'libtool_flag' => 'OBJCXX',
'lder' => 'OBJCXXLD',
'ld' => '$(OBJCXX)',
'pure' => 1,
Information forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Sun, 03 Dec 2023 02:12:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 67539 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 30 Nov 2023 22:45, Nick Bowler wrote:
> Interestingly the libtool manual also says "If [libtool] can't infer a
> tag, then it defaults to the configuration for the C language", which is
> clearly not the case (it seems what actually happens is that if libtool
> can't infer a tag then it exits with a fatal error). So I wonder if
> this is actually a regression in libtool.
i'm fairly certain libtool used to do this aaaaaaaaaages ago, and i *think*
it stopping was intentional. i recall a lot of pain in Gentoo from that
switchup, but tbh, i don't think any of it was "wrong" ... all the fixes we
landed were because the code was being misused/abused, and silently doing
the wrong thing (especially when cross-compiling). so i personally prefer
the new world order, and would say we should lobby for the manual to change
rather than rollback the behavior.
-mike
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Sun, 10 Dec 2023 21:37:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 67539 <at> debbugs.gnu.org (full text, mbox):
partially related to how Automake is calling libtool from the
build rules (it is missing the --tag option),
I added the tags to automake as previously posted here.
(https://debbugs.gnu.org/cgi/bugreport.cgi?bug=67539)
no tag defined for Objective C[1] (presumably it would be --tag=OBJC)
...
"If [libtool] can't infer a tag, then it defaults to the
configuration for the C language"
...
lobby for the manual to change rather than rollback the behavior.
I wrote bug-libtool about these things.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=67754
Thanks,
Karl
Information forwarded
to
bug-automake <at> gnu.org
:
bug#67539
; Package
automake
.
(Mon, 25 Dec 2023 23:40:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 67539 <at> debbugs.gnu.org (full text, mbox):
Closing this since there's nothing left to do on the automake side.
(Someone new volunteered to take over libtool, BTW, but I see no changes
in the maintainers file as yet. Not sure where that stands.) --best, karl.
Reply sent
to
Karl Berry <karl <at> freefriends.org>
:
You have taken responsibility.
(Mon, 25 Dec 2023 23:40:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Dennis Clarke <dclarke <at> blastwave.org>
:
bug acknowledged by developer.
(Mon, 25 Dec 2023 23:40:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 23 Jan 2024 12:24:07 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 134 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.