On 2018-10-02 09:31:33 -0400, Nick Bowler wrote:
> Drilling into the Autoconf source, we find that this is intentional:
>
> # The AC_TRY_EVAL and AC_TRY_COMMAND macros are dangerous and
> # undocumented, and should not be used.
> # They may be removed or their API chan
On 10/2/18, Vincent Lefevre wrote:
> I originally reported this bug in libtool:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21309
>
> but this actually seems to be a bug in AC_TRY_EVAL (or another macro
> it uses).
AC_TRY_EVAL is not documented in the Autoconf
I originally reported this bug in libtool:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21309
but this actually seems to be a bug in AC_TRY_EVAL (or another macro
it uses).
Under Debian/unstable, with autoconf 2.69, I get binary data in the
config.log for MPFR due to \1 and \2 in echo
Hallo Ralf,
On 7 Aug 2010, at 15:20, Ralf Wildenhues wrote:]
AC_TRY_EVAL is undocumented, but I don't see equivalent functionality
that Automake (and Libtool) can use to try and log test commands.
So, I guess I'm asking to either let this not die, or provide a similar
but safer new API
