[Top][All Lists]

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

Re: use of AC_TRY_EVAL broken

From: Ralf Wildenhues
Subject: Re: use of AC_TRY_EVAL broken
Date: Fri, 24 Oct 2008 21:51:26 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

* Eric Blake wrote on Fri, Oct 24, 2008 at 04:15:34AM CEST:
> According to Bruno Haible on 10/23/2008 5:09 PM:
> > There is a need for autoconf macros to compile and execute programs that
> > they have created with AC_LANG_CONFTEST
> >   1) without having to build up the compile or link command by itself,
> >   2) with log of the command and its error messages and exit code to the log
> >      file.
> Yes, but it probably should not be named AC_TRY_EVAL, so that existing
> uses of the undocumented and broken interface aren't themselves broken
> when we close the security hole in whatever we document.

Here's to consistency (and to the demise of all AC*TRY* macros ;-)
a suggestion for a new name: AC_EVAL_IFELSE.

> In particular, AC_TRY_EVAL is an undocumented interface which, in the
> autoconf sources itself, mentions that it is unsafe and may be
> withdrawn or changed in the future.

Obsoletion: ok, once gettext, gnulib, and libtool are free of them.
Withdrawal: patience, please.

Thanks a lot!

reply via email to

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