Package: setools
Version: 3.3.4.ds-3
As you can confirm looking at the build logs of this package, configure
is run once when the buildd runs build and a second time when the buildd
calls the binary target (where it should not).
I think the root reason for this is the following misconception in
debian/common/targets.mk:
# Next, all targets that have work performed in them do not have stamp
# files on their own, and thus are not depended on directly by other
# targets. Instead, they depend on and are depended up by intermediate
# targets in which no work is done except to create stamp files. Other
# targets just depend on the stamp files; so the build system does not do
# work twice -- targets, which are up to date, are not executed again.
As all (well most of) the -stamp files depend thus on phony rules, make
never thinks they are up to date.
The actual reason are a bit more complex. For example the
"stamp-conf/setools:" rule is phone because it does not generate
"stamp-conf/setools" but "stamp-conf", thus being called again.
As CONFIG-common is phony because of testdir (which by the way looks
a bit empty), the stamp-arch-conf files are also phony.
On the other hand, your build/setool target has no prerequisites
at all, thus calling "./debian/rules build/setools" results in an
error instead of doing the other needed steps before.
(Calling directly might not look very sensible, but this also means
that this package does save to be called with -j and values larger 1,
as in that case make might decide this sub-target is a nice thing
to employ the second processor while the first does all the lasting
configure runs).
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
