[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU make troubleshooting
From: |
Eli Zaretskii |
Subject: |
Re: GNU make troubleshooting |
Date: |
Tue, 11 Jul 2023 05:38:29 +0300 |
> From: Jeffrey Walton <noloader@gmail.com>
> Date: Mon, 10 Jul 2023 16:34:49 -0400
> Cc: bug-make@gnu.org
>
> I would add GNU's make lacks minimal debug facilities.
I think "make -p" and "make -d" do provide ample debugging
capabilities.
> I think trace is worthless. It does not help the folks writing
> makefiles. Or it has never helped me understand why a statement was
> (or was not) evaluated, or the result of the evaluation.
Then you should be free not to use that option. I personally think it
does help in some situations.
Re: GNU make troubleshooting, Jeffrey Walton, 2023/07/10
- Re: GNU make troubleshooting, Paul Smith, 2023/07/10
- Re: GNU make troubleshooting, Jeffrey Walton, 2023/07/10
- Re: GNU make troubleshooting, Paul Smith, 2023/07/11
- Re: GNU make troubleshooting, Jeffrey Walton, 2023/07/11
- Re: GNU make troubleshooting, Alejandro Colomar, 2023/07/11
- Re: GNU make troubleshooting, Paul Smith, 2023/07/11
Re: GNU make troubleshooting,
Eli Zaretskii <=
Re: GNU make troubleshooting, Dmitry Goncharov, 2023/07/15
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/15
- Re: GNU make troubleshooting, Dmitry Goncharov, 2023/07/15
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/15
- Re: GNU make troubleshooting, David Boyce, 2023/07/15
- Re: GNU make troubleshooting, Dmitry Goncharov, 2023/07/16
- Re: GNU make troubleshooting, Bruno Haible, 2023/07/17
Re: MAKEFLAGS=-r, Bruno Haible, 2023/07/17
Re: MAKEFLAGS=-r, David Boyce, 2023/07/17
Re: MAKEFLAGS=-r, Bruno Haible, 2023/07/17