GNU bug report logs -
#60508
archive DEPENDENCIES incorrectly depends on ordering
Previous Next
Full log
View this message in rfc822 format
[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)]
This bug report was last modified 2 years and 154 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.