[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf-2.71: declaration ordering problem: ac_fn_c_try_run () is d
|
From: |
Nick Bowler |
|
Subject: |
Re: autoconf-2.71: declaration ordering problem: ac_fn_c_try_run () is defined, but after attempted use |
|
Date: |
Thu, 1 Apr 2021 12:06:04 -0400 |
On 2021-04-01, Ondrej Dubaj <odubaj@redhat.com> wrote:
> experiencing configure problem
>
> ./configure: line 18777: ac_fn_c_try_run: command not found
>
> It seems that CMU_HAVE_OPENSSL brings CMU_FIND_LIB_SUBDIR brings
> AC_CHECK_SIZEOF(long) ... that brings the use of *check_int and that
> brings the use of ac_fn_c_try_run ... but it doesn't bring the macro
> defining it.
These sort of issues are typically caused by underquoting, probably
within the definition of CMU_HAVE_OPENSSL and/or CMU_FIND_LIB_SUBDIR.
Due to technical limitations of m4, AC_REQUIRE does not work properly
when it is expanded during argument collection. This is not usually
a problem when arguments are quoted properly: one of the reasons
why proper quoting is so important.
> IMO there's something wrong with calling AC_TRY_RUN in AC_CACHE_VAL.
If you could share the code in question, I can give more specific
comments. But my totally wild guess is that the second argument to
AC_CACHE_VAL is not quoted.
Cheers,
Nick