Bug#628515: recommending verbose build logs
- To: 628515@bugs.debian.org
- Subject: Bug#628515: recommending verbose build logs
- From: Jonathan Nieder <jrnieder@gmail.com>
- Date: Mon, 16 Jan 2012 23:34:54 -0600
- Message-id: <[🔎] 20120117053454.GA9483@burratino>
- Reply-to: Jonathan Nieder <jrnieder@gmail.com>, 628515@bugs.debian.org
- In-reply-to: <87vcq4qbqy.fsf@windlord.stanford.edu>
- References: <4DE2898E.4040206@debian.org> <20111127003703.GA9986@elie.hsd1.il.comcast.net> <20111127101542.GA1868@jwilk.net> <20111127103933.GA23290@elie.hsd1.il.comcast.net> <20111128110955.GB23853@yellowpig> <87vcq4qbqy.fsf@windlord.stanford.edu>
Russ Allbery wrote:
> What should we do about cases where the upstream build system makes it
> difficult to override the verbosity? In other words, is this a place
> where we should push Debian package maintainers to actually fix the
> upstream build system to make build logs verbose even if upstream doesn't
> support that as an option? I'm thinking, for example, of some of djb's
> public domain software, where the compiler invocation is stored in a shell
> script
Good question. IMHO yes, we should encourage packagers to help
upstream provide an option that makes the logs indicate how the
compiler was invoked, to make reproducing and debugging problems
easier.
In the kind of build system you're talking about, something like
[ -z "$V" ] || set -x
at the top of the compiler invocation script could do the trick.
Reply to: