Re: GNU make 4.2.90 release candidate available

[Paul Smith]

Sorry, I didn't mean you needed to explain all these options to me :).

In particular I was wondering about the CPPFLAGS, because attempting to
add reserved preprocessor options to the compile line can cause
problems in system header files.  Also, by adding a new include
directory to search, there could be files in that include directory
which overlap with/conflict with headers that are expected by make
and/or the operating system.

In my work doing system/embedded/cross-compilation systems I've seen
MANY cases where these sorts of options cause strange and unexpected
behavior.

Note, make is not multithreaded so options that manage pthread etc. are
not relevant to it (but shouldn't hurt either).

If the /opt/dw directory is empty then clearly that's not a problem.

Given that we're seeing a lot of strange and unexpected behavior I just
thought it might be helpful to remove all the customizations and start
with a "clean slate" to get a baseline.

If you're confident that's not necessary, that's fine too.

>  > If it chooses the one that comes with GNU make, you will see the error
>  > (!!) because our glob/fnmatch is too old. >
> 
> How do we force the usage of the system version ?

I'm not sure there's any way to do that... well, you can pre-seed the
config cache but it's gross.  But, all the GNU/Linux ones I looked at
seemed to be using the system libc anyway so I don't think it's an
issue.