On Fri, 2022-01-28 at 01:09 +0100, Alejandro Colomar (man-pages) wrote:
> I'd like make to warn about this. It took me a while to debug
> a Makefile bug, which I thought was not happening, since make should
> have warned me. Isn't this supposed to trigger the warning?
In previous versions of GN
Hi Paul,
On 1/28/22 23:49, Paul Smith wrote:
> On Fri, 2022-01-28 at 01:09 +0100, Alejandro Colomar (man-pages) wrote:
>> I'd like make to warn about this. It took me a while to debug
>> a Makefile bug, which I thought was not happening, since make should
>> have warned me. Isn't this supposed
Hi Martin,
On 1/28/22 02:42, Martin Dorey wrote:
> That already seems to have been fixed:
Hmm, it seems that the bug is only triggered if the option is passed in
the Makefile itself with MAKEFLAGS+=...
I haven't tested make git HEAD, but I bet it's probably reproducible
there too. See below.
T
g-make@gnu.org
Subject: [BUG] --warn-undefined-variable is not triggered in prerequisites
* EXTERNAL EMAIL *
Hi,
Consider the following scenario:
$ ls
Makefile
$ cat Makefile
MAKEFLAGS += --warn-undefined-variables
a: $(foo)
touch $@
$ make
touch a
$ ls
a Makefile
I'd
Hi,
Consider the following scenario:
$ ls
Makefile
$ cat Makefile
MAKEFLAGS += --warn-undefined-variables
a: $(foo)
touch $@
$ make
touch a
$ ls
a Makefile
I'd like make to warn about this. It took me a while to debug a
Makefile bug, which I thought was not happening, since make sh
