Carlos O'Donell wrote:
> (a) logf
> (b) log10f
>
> Why wasn't -lm added to the link?
>
> This looks like an environment/configuration issue with gnulib.
>
> Adding `-lm' to CC fixes this, but that can't be right.
>
> configure:84449: checking whether log10f works according to ISO C 99 with IEC
> 60559
> configure:84504: gcc
> -Wl,-rpath=/scratch/carloso/build4-lucid-cs/install//lib64:/scratch/carloso/build4-lucid-cs/install//usr/lib64
>
> -Wl,--dynamic-linker=/scratch/carloso/build4-lucid-cs/install//lib64/ld-linux-x86-64.so.2
> -std=gnu99 -o conftest -g -O2 -nostdinc
> -I/usr/local/tools/gcc-4.3.3/lib/gcc/x86_64-unknown-linux-gnu/4.3.2/include-fixed
> -I/scratch/carloso/build4-lucid-cs/install//usr/include
> -I/usr/local/tools/gcc-4.3.3/lib/gcc/x86_64-unknown-linux-gnu/4.3.2/include
> -Wall conftest.c >&5
> /tmp/cceWScoH.o: In function `main':
> /tmp/testdir/conftest.c:632: undefined reference to `log10f'
> collect2: ld returned 1 exit status
> configure:84508: $? = 1
> configure: program exited with status 1
> configure: failed program was:
> ...
> configure:84537: result: no
I can't see why LOGF_LIBM would have been empty. But for (b), it is a
consequence of (a) and a small bug in gnulib, which I'm fixing here.
2012-06-28 Bruno Haible <br...@clisp.org>
log10f: Fix possible configuration problem.
* m4/log10f.m4 (gl_FUNC_LOG10F): Augment LIBS by $LOG10F_LIBM, not
$LOGF_LIBM.
Reported by Carlos O'Donell <carlos_odon...@mentor.com>.
--- m4/log10f.m4.orig Thu Jun 28 21:58:37 2012
+++ m4/log10f.m4 Thu Jun 28 21:58:15 2012
@@ -1,4 +1,4 @@
-# log10f.m4 serial 5
+# log10f.m4 serial 6
dnl Copyright (C) 2011-2012 Free Software Foundation, Inc.
dnl This file is free software; the Free Software Foundation
dnl gives unlimited permission to copy and/or distribute it,
@@ -38,7 +38,7 @@
[gl_cv_func_log10f_ieee],
[
save_LIBS="$LIBS"
- LIBS="$LIBS $LOGF_LIBM"
+ LIBS="$LIBS $LOG10F_LIBM"
AC_RUN_IFELSE(
[AC_LANG_SOURCE([[
#ifndef __NO_MATH_INLINES
