>>>>> On Mon, 02 Sep 2019 12:28:52 -0400, Paul Smith <psm...@gnu.org> said:
Paul> My first guess is that this another of a series of unpleasantnesses
Paul> caused by clang trying to "pretend" to be GCC, and failing.
Paul> I understand why the Clang devs do this: they want to take advantage
of
Paul> the built-in userbase for GCC software. But it's extremely painful
for
Paul> portability since clang is NOT GCC.
Paul> If you run "./configure CC=clang" instead of allowing it to find the
Paul> "gcc" wrapper that Apple installs, does it work properly?
No, clang gets invoked with the same flags, and fails the same way.
Paul> This behavior (invoking GCC using these flags) is part of the automake
Paul> package, not GNU make itself, so it will be very painful for us to
work
Paul> around.
Yes. Plus removing '-C' from AM_CFLAGS reveals that there are other
flags that clang doesnʼt like.
The good news is that this affects only building from git, the
pre-release tarball builds fine with just './configure', and passes
all but one test from 'make check'.
Robert
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
