No reaction since 3.5 years. Bug still persists.
On Mon, Apr 25, 2016 at 8:48 PM Bert Wesarg wrote:
>
> Dear Autotconf developers,
>
> I just realized, that the cache variable name for AC_CHECK_LIBS does
> not conform to the documented one if AS_LITERAL_WORD_IF fails for the
>
ompiler_gnu=$ac_cv_fc_compiler_gnu
--
2.17.0.591.ge996b92f55
On Sat, Dec 1, 2018 at 3:39 PM Bert Wesarg wrote:
>
> ,Dear all,
>
> AC_LANG(Fortran) uses the above parameter expansion to set `ac_ext`, see here:
>
>
> http://git.savannah.gnu.org/cgit/autoconf.git/tree/lib/au
,Dear all,
AC_LANG(Fortran) uses the above parameter expansion to set `ac_ext`, see here:
http://git.savannah.gnu.org/cgit/autoconf.git/tree/lib/autoconf/fortran.m4#n223
Though I consider it harmful, because if $ac_fc_srcext is set but null
the value of ac_ext is also null.
That problem ar
On Thu, Mar 16, 2017 at 11:26 PM, Nick Bowler wrote:
> Hello,
>
> On 2017-03-16, Max Horn wrote:
>> on
>> https://www.gnu.org/software/autoconf/manual/autoconf.html#Using-System-Type
>>
>> this example is given:
>>
>> case $host in
>>alpha*-*-*) AC_CONFIG_LINKS([dither.c:alpha/dith
resides.
$ cat build/srcdir
srcdir=../../build
This one also looks correct, @srcdir@ points to 'build'.
$ cat test/srcdir-build
srcdir=../../../../build/../test
But this one is broken. It does not to resolve an valid path at all.
Am I doing something wrong, or is something broken in autoconf?
Thanks for any advice.
Kind Regards,
Bert Wesarg