[Top][All Lists]

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

Re: Patches for implementing checking for valid CFLAGS, LDFLAGS, etc.

From: Maarten Bosmans
Subject: Re: Patches for implementing checking for valid CFLAGS, LDFLAGS, etc.
Date: Sat, 25 Jun 2011 12:01:08 +0200

Hi Peter,

2011/6/25 Peter Simons <address@hidden>:
> I have pushed your patches to the Git repository moments ago. Thank you
> very much for your efforts!


If there were some submission guidelines stating the width of
description lines and how to properly mark a macro deprecated, I could
have done that before submitting the patches. The current guidelines
on the website only seem  to cover completely new macro submissions.

>  > There are some AX_APPEND_* macros added, should these be in the same
>  > file or separate?
> If at all possible, there should be just one macro per m4 file. That
> policy allows tools like aclocal(1) to pull macros into a project with
> high precision. Also, it means that the name of the macro matches the
> name of the m4 file, which makes things easier for the user.

OK, that sounds reasonable. I'm OK with the current situation though,
but if anyone wants to extract the AX_APPEND_* macros to a new file,
feel free. Note that the AX_APPEND_{COMPILE,LINK}_FLAGS macros depend
on both AX_APPEND_FLAG and the respective AX_CHECK_*_FLAG macros.

>  > For ax_check_*_flags and ax_*_check_flag I used AU_DEFUN to provide
>  > an implementation based on the new macros that is automatically
>  > updated when running autoupdate. Is this the right approach, or
>  > should I leave the deprecated macros as the were and only add a
>  > message on top of the description?
> Using AU_DEFUN to replace obsolete macros with the newer version is very
> desirable. Yes, please do that! :-)

About the snippet you added to NEWS:
>  The new macro AX_CHECK_FLAG has been added, which replaces AX_C_CHECK_FLAG,
>  AX_CXXCPP_CHECK_FLAG, and AX_LD_CHECK_FLAG. Further details can be found at
> <>.

The macro is not called AX_CHECK_FLAG, that is the name of the file
that contains AX_CHECK_COMPILE_FLAG and others. You could spell it in
lowercase to signify that it's the file we're talking about, not the

not really replaced by AX_CHECK_COMPILE_FLAG. That macro is merely
used in their implementation to abstract out all the commonalities of
the individual compiler macros. The thing they add on top is knowledge
about the compiler-specific flags to treat unknown options as errors.
The remark at te bottom of my first mail about further improvements in
these macros is still valid, as this compiler-specific knowledge is
still encoded multiple times in other macros and I think it should be
in one central place in the autoconf archive.
But that is work for a later day (or someone else).


> Again, thank you very much for your efforts!
> Take care,
> Peter

reply via email to

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