Re: GNU make troubleshooting

2023-08-27 Thread Alejandro Colomar
Hi Paul, On 2023-08-27 15:52, Paul Smith wrote: > On Sun, 2023-08-27 at 15:47 +0200, Alejandro Colomar wrote: >> In fact, I'm going to define .SILENT always in the Linux man-pages, >> since V=1 is just an unnecessary duplicate for --degub=print. >> I'll make V=1 only have the effect of

Re: GNU make troubleshooting

2023-08-27 Thread Paul Smith
On Sun, 2023-08-27 at 15:47 +0200, Alejandro Colomar wrote: > In fact, I'm going to define .SILENT always in the Linux man-pages, > since V=1 is just an unnecessary duplicate for --degub=print. > I'll make V=1 only have the effect of redirecting stderr of certain > programs. Just be aware that

Re: GNU make troubleshooting

2023-08-27 Thread Paul Smith
On Sun, 2023-08-27 at 16:33 +0300, Eli Zaretskii wrote: > That error code 2 means file not found, and -1 means a command was > not found or completely failed to run.  It is easy to show a couple > of examples for each one, we see those every day. That might be true in Windows but it's not the

Re: GNU make troubleshooting

2023-08-27 Thread Alejandro Colomar
On 2023-08-27 15:35, Alejandro Colomar wrote: > On 2023-08-27 15:33, Paul Smith wrote: >> On Sun, 2023-08-27 at 09:26 -0400, Paul Smith wrote: >>> Yes, that's a good idea to mention .SILENT. >> >> Actually I think I will simply recomment using --debug=print instead as >> that's simpler. > > LGTM.

Re: GNU make troubleshooting

2023-08-27 Thread Alejandro Colomar
On 2023-08-27 15:33, Paul Smith wrote: > On Sun, 2023-08-27 at 09:26 -0400, Paul Smith wrote: >> Yes, that's a good idea to mention .SILENT. > > Actually I think I will simply recomment using --debug=print instead as > that's simpler. LGTM. That's much better, as you don't modify the Makefile,

Re: GNU make troubleshooting

2023-08-27 Thread Eli Zaretskii
> From: Paul Smith > Cc: br...@clisp.org, bug-make@gnu.org > Date: Sun, 27 Aug 2023 09:16:59 -0400 > > On Sun, 2023-08-27 at 08:51 +0300, Eli Zaretskii wrote: > > This checklist is very useful, but to make it even more useful, it > > lacks two things: > > > >  . an example of error message that

Re: GNU make troubleshooting

2023-08-27 Thread Paul Smith
On Sun, 2023-08-27 at 09:26 -0400, Paul Smith wrote: > Yes, that's a good idea to mention .SILENT. Actually I think I will simply recomment using --debug=print instead as that's simpler. -- Paul D. Smith Find some GNU make tips at: https://www.gnu.org

Re: GNU make troubleshooting

2023-08-27 Thread Paul Smith
On Sun, 2023-08-27 at 15:21 +0200, Alejandro Colomar wrote: > Maybe mention that removing .SILENT: would be necessary, if > it is defined.  Here's what the Linux man-pages makefiles do. Yes, that's a good idea to mention .SILENT. I really don't want to get into documenting all the different ways

Re: GNU make troubleshooting

2023-08-27 Thread Alejandro Colomar
Hi Paul, On 2023-08-27 15:16, Paul Smith wrote: > On Sun, 2023-08-27 at 08:51 +0300, Eli Zaretskii wrote:> >> Removing @ is not always enough. Many makefiles nowadays need you to >> say "make V=1" to override the default verbosity level. I suggest to >> mention that. > > What does "V=1" do,

Re: GNU make troubleshooting

2023-08-27 Thread Paul Smith
On Sun, 2023-08-27 at 08:51 +0300, Eli Zaretskii wrote: > This checklist is very useful, but to make it even more useful, it > lacks two things: > >  . an example of error message that indicates each kind of problem >  . a cross-reference to where the details are There is a menu of links to each

Re: GNU make troubleshooting

2023-08-27 Thread Alejandro Colomar
Hi Paul, On 2023-08-26 18:48, Paul Smith wrote: > I added a new appendix to the GNU make manual for troubleshooting help; > I haven't pushed it yet. See below. Comments welcome. > > I think the outline you provided earlier, Bruno, has the problem that a > lot of it isn't really about