[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Wrong order of preprocessor and compiler flags
From: |
Zack Weinberg |
Subject: |
Re: Wrong order of preprocessor and compiler flags |
Date: |
Wed, 23 Mar 2022 17:16:42 -0400 |
User-agent: |
Cyrus-JMAP/3.5.0-alpha0-4911-g925b585eab-fm-20220323.003-g925b585e |
On Wed, Mar 23, 2022, at 11:31 AM, Evgeny Grin wrote:
> Hello,
>
> I've found that everywhere in autoconf scripts flags are used like:
> $CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&AS_MESSAGE_LOG_FD
> while automake and libtool use flags in the other order:
> $(CC) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS)
> $(AM_CFLAGS) $(CFLAGS)
I agree that this should be made consistent, but before we change anything, we
need to check what the rules *built into GNU and BSD Make* do with CFLAGS and
CPPFLAGS (and also CXXFLAGS, OBJCFLAGS, etc) because those are much much harder
to get changed than anything in Automake or Autoconf, so we should aim to
harmonize everything with them.
Can you look into that please, Evgeny?
zw
Re: Wrong order of preprocessor and compiler flags, Evgeny Grin, 2022/03/24