GNU bug report logs - #60508
archive DEPENDENCIES incorrectly depends on ordering

Previous Next

Package: automake;

Reported by: Mike Frysinger <vapier <at> gentoo.org>

Date: Tue, 3 Jan 2023 04:33:02 UTC

Severity: normal

Tags: confirmed, help

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

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-automake <at> gnu.org:
bug#60508; Package automake. (Tue, 03 Jan 2023 04:33:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Mike Frysinger <vapier <at> gentoo.org>:
New bug report received and forwarded. Copy sent to bug-automake <at> gnu.org. (Tue, 03 Jan 2023 04:33:02 GMT) Full text and rfc822 format available.

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

From: Mike Frysinger <vapier <at> gentoo.org>
To: bug-automake <at> gnu.org
Subject: archive DEPENDENCIES incorrectly depends on ordering
Date: Mon, 2 Jan 2023 23:32:24 -0500
[Message part 1 (text/plain, inline)]
i have a project that generates a bunch of arch-specific archives.  i also have
an intermediate archive for holding common objects (so only need to build them
once).  i noticed that while (ab)using LIBADD & OBJECTS variables, Automake
incorrectly omits propagating OBJECTS variables from LIBADD to DEPENDENCIES if
the library using the OBJECTS comes before the library defining the OBJECTS.

attaching a testcase to run against current git that triggers the bug that
hopefully makes it a little clearer:
* libmMID.a defines a bunch of common objects
* libaFIRST.a and libzLAST.a adds libmMID.a's objects to its libadd
* libaFIRST.a's dependency is *missing* the objects, but libzLAST.a has them

$ ./pre-inst-env ./runtest t/ar-dep.sh
...
+ grep _a_DEPENDENCIES = Makefile.in
libaFIRST_a_DEPENDENCIES =
libzLAST_a_DEPENDENCIES = $(libmMID_a_OBJECTS)
+ grep ^libzLAST_a_DEPENDENCIES = $(libmMID_a_OBJECTS) Makefile.in
libzLAST_a_DEPENDENCIES = $(libmMID_a_OBJECTS)
+ grep ^libaFIRSTT_a_DEPENDENCIES = $(libmMID_a_OBJECTS) Makefile.in
+ am_exit_trap 1
...
-mike
[ar-dep.sh (application/x-sh, attachment)]
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-automake <at> gnu.org:
bug#60508; Package automake. (Tue, 03 Jan 2023 22:17:01 GMT) Full text and rfc822 format available.

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

From: Karl Berry <karl <at> freefriends.org>
To: vapier <at> gentoo.org
Cc: 60508 <at> debbugs.gnu.org
Subject: Re: bug#60508: archive DEPENDENCIES incorrectly depends on ordering
Date: Tue, 3 Jan 2023 15:16:30 -0700
Hi Mike - thanks for the report.

    * libmMID.a defines a bunch of common objects
    * libaFIRST.a and libzLAST.a adds libmMID.a's objects to its libadd
    * libaFIRST.a's dependency is *missing* the objects, but libzLAST.a
    has them

Yikes. Well, if you or anyone can find a patch, that would be great.
Else I'll look at it when I have a chance (not soon, unfortunately).
--thanks again, karl.




Added tag(s) confirmed and help. Request was from Mike Frysinger <vapier <at> gentoo.org> to control <at> debbugs.gnu.org. (Fri, 13 Jan 2023 05:38:02 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 96 days ago.

Previous Next


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