bug-make
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU make 4.2.90 release candidate available


From: Paul Smith
Subject: Re: GNU make 4.2.90 release candidate available
Date: Mon, 02 Sep 2019 12:28:52 -0400
User-agent: Evolution 3.32.1-2

On Mon, 2019-09-02 at 18:20 +0200, Robert Pluim wrote:
> is this intended to build on macOS using clang, or using gcc only?

It should work with any C compiler that supports the C89 standard.
 
> $ gcc --version
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr 
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 10.0.1 (clang-1001.0.46.4)
> Target: x86_64-apple-darwin18.7.0
> Thread model: posix
> InstalledDir: /Library/Developer/CommandLineTools/usr/bin
> 
> $ make
> Making all in lib
> /Library/Developer/CommandLineTools/usr/bin/make  all-recursive
> make[3]: Nothing to be done for `all-am'.
> Making all in po
> make[1]: Nothing to be done for `all'.
> Making all in doc
> make[1]: Nothing to be done for `all'.
> depbase=`echo src/ar.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
>         gcc -DHAVE_CONFIG_H   -Isrc -I./src -Ilib -I./lib 
> -DLIBDIR=\"/usr/local/lib\" -DINCLUDEDIR=\"/usr/local/include\" 
> -DLOCALEDIR=\"/usr/local/share/locale\"  -DMAKE_MAINTAINER_MODE 
> -I/usr/local/include  -C -Wall -Wextra -Werror -Wwrite-strings -Wshadow 
> -Wdeclaration-after-statement -Wbad-function-cast -Wformat-security 
> -Wtype-limits -Wunused-but-set-parameter -Wlogical-op -Wpointer-arith 
> -Wignored-qualifiers -Wformat-signedness -Wduplicated-cond -g -O2 -MT 
> src/ar.o -MD -MP -MF $depbase.Tpo -c -o src/ar.o src/ar.c &&\
>         mv -f $depbase.Tpo $depbase.Po
> clang: error: invalid argument '-C' only allowed with '-E'

My first guess is that this another of a series of unpleasantnesses
caused by clang trying to "pretend" to be GCC, and failing.

I understand why the Clang devs do this: they want to take advantage of
the built-in userbase for GCC software.  But it's extremely painful for
portability since clang is NOT GCC.

If you run "./configure CC=clang" instead of allowing it to find the
"gcc" wrapper that Apple installs, does it work properly?

This behavior (invoking GCC using these flags) is part of the automake
package, not GNU make itself, so it will be very painful for us to work
around.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]