[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #59169] Add a --debug=why category for the -d/--debug option

From: Paul D. Smith
Subject: [bug #59169] Add a --debug=why category for the -d/--debug option
Date: Sat, 26 Sep 2020 17:03:25 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36

Follow-up Comment #1, bug #59169 (project make):

I don't fully remember why I created --trace as a separate option.  I think
the idea was that it would be useful for "normal users" who weren't trying to
debug makefiles, but rather were trying to trace their build operations, so
putting it under --debug seemed like people might not find it.  Not sure.

Probably the right thing to do is create a debug flag that is specifically for
showing command lines even if they are marked as "don't print", and have a
debug flag such as you've added which shows information on why a rule was

Then, have the --trace flag set both those options.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]