Eric Blake wrote:
> I'm thinking of removing AC_TRY_EVAL from the
> next version of autoconf because of its security risks.
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.
Please document such a facility.
In gnulib and gettext we find many uses of
AC_TRY_EVAL([ac_link])
but also one with a command of its own:
ac_gcj_link="$GCJ $GCJFLAGS conftest.java --main=conftest -o conftest$ac_exeext"
AC_TRY_EVAL([ac_gcj_link])
In libtool you find many uses of
AC_TRY_EVAL(ac_compile)
and
AC_TRY_EVAL(ac_link)
but also two more complicated ones:
AC_TRY_EVAL(NM conftest.$ac_objext \| $lt_cv_sys_global_symbol_pipe \> $nlist)
AC_TRY_EVAL(_LT_TAGVAR(archive_cmds, $1) 2\>\&1 \| $GREP \" -lc \" \>/dev/null 2\>\&1)
So, not only AC_TRY_EVAL should be documented, but also the variables 'ac_link'
and 'ac_compile'.
Bruno
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
