Hello Jonathan, On Wed 01 Aug 2018 at 10:47PM -0700, Jonathan Nieder wrote:
> Thanks for reporting. My understanding from > https://bugs.debian.org/628515 is that the intention is > > - print out compiler driver command lines, so that compiler errors are > closely preceded with the command that produced them > > - no need to print out command lines for tools like ld that are > themselves invoked by the compiler driver, but do print out those > command lines if you invoke them directly > > I don't think verbosity for the sake of verbosity was ever a goal > here, so ideas for better wording would be very welcome. > > In https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628515;msg=30 > I proposed wording along the lines of > > <tag>terse</tag> > <item> > Compiler and linker commands used to build the package > should not be abbreviated in the log unless this > tag is supplied. > > Packages built with <tt>cmake</tt>, autotools, or > the Linux kernel build system can implement this by > passing the parameters <tt>V=1</tt> and > <tt>VERBOSE=1</tt> by default as arguments to > <tt>make</tt> and omitting them when the terse tag is > supplied. > </item> > > I am not sure why this suggestion got generalized to "as verbose as > reasonably possible" in the patch that replaced it. IIRC my hope was to generalise the recommendation to apply to as many different build systems as possible. For example, packages whose builds do not involve any compilers and linkers. We could restore your text in a footnote or a "For example ..." paragraph? -- Sean Whitton
signature.asc
Description: PGP signature
