On 08/24/2011 09:36 PM, Joey Hess wrote: > Matthias Klose wrote: >> dh build >> dh_testdir >> dh_auto_configure >> checking which defines needed for makedepend... >> checking for a BSD-compatible install... /usr/bin/install -c >> checking for gcc... gcc >> [...] > > If configure fails, dh_auto_configure dumps the whole config.log, > which includes the configure command.
which I assume only works with the toplevel configure? >> dh_auto_build >> make[1]: Entering directory >> `/build/buildd-socat_1.7.1.3-1.1-armel-IsVcwK/socat-1.7.1.3' >> gcc -g -O2 -D_GNU_SOURCE -Wall -Wno-parentheses -DHAVE_CONFIG_H -I. -I. >> -c >> -o socat.o socat.c >> [...] > > This tends to not be very interesting (ie, just "make" 99% of the time > or "ant" 1%) and is also printed when there is an error. well, I do disagree. So to know how a package was configured, I have to build it locally with DH_VERBOSE, just to know how it was built? why obfuscate the build log in such a way by default? Matthias -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
