3 ms·

Do note that GNU make is still being developed. It even had breaking changes in the recent 4.4 release. Also GNU make 4.3 has at least one bug (e.g. on Ubuntu 2

Do note that GNU make is still being developed. It even had breaking changes in the recent 4.4 release. Also GNU make 4.3 has at least one bug (e.g. on Ubuntu 22.04) where tgt: gcc hello errors when you have a directory with the name gcc in your PATH. (This is a bug in gnulib, that’s fixed, but gnulib is a rolling release typically vendored by every project on an arbitrary commit, sigh) Also system GNU make on Ubuntu 20.04 has a bug in —-output-sync. It doesn’t sync. And finally GNU make on macOS is ancient by default. Like over a decade old. So what works on Linux may not always work on macOS.

u801e 4y ago
> Also GNU make 4.3 has at least one bug (e.g. on Ubuntu 22.04) where > > tgt: > gcc hello > > errors when you have a directory with the name gcc in your PATH. The make documentation examples use the CC variable to point to the path of the compiler. That is: CC=/usr/bin/gcc Did the bug you mention also affect make files using variables to refer to the compiler program path in rule recipies?
- stabbles 4y ago
  Not sure what happens in the case of CC=gcc and $(CC) ..., but in any case, this is the bug: https://savannah.gnu.org/bugs/index.php?57962 https://savannah.gnu.org/bugs/index.php?57962