Re: avoiding obsolete macros like AC_TRY_RUN

[Bruno Haible]

Hi Ralf,

Coming back to our discussion of AC_TRY_RUN etc. in
[1] <http://lists.gnu.org/archive/html/bug-gnulib/2009-09/msg00042.html>
[2] <http://lists.gnu.org/archive/html/bug-gnulib/2009-09/msg00056.html>

I now realized that "autoconf -Wall" is giving warnings because of
gettext.m4, intl.m4, and similar, which are shared between gettext and
gnulib.

I'm considering to replace the uses of AC_TRY_RUN etc. for this reason.

But I have to come back to the drawbacks of AC_*_IFELSE (item 1 in [1]).

> I agree on the less-than-ideal naming of the AC_*_IFELSE macros.

Good. Do you have any plans to achieve a better naming?

> >      - Pitfall: It's easy to forget the invocation of AC_LANG_SOURCE, and 
> > then
> >        autoconf generates code which will fail on many but not all 
> > platforms.
> 
> We should think about what we can do to address this, thanks for the
> suggestion.

Have you or the other Autoconf developers found a way to address this?

> Users of your macros have to live with the constant set of warnings
> about obsolete macro usage

The attached patches will fix this.

Bruno

0001-Modernize-AC_TRY_COMPILE-invocations.patch.gz
Description: GNU Zip compressed data

0002-Modernize-AC_TRY_LINK-invocations.patch.gz
Description: GNU Zip compressed data

0003-Modernize-AC_TRY_RUN-invocations.patch.gz
Description: GNU Zip compressed data