* Vincent Torri wrote on Mon, Oct 27, 2008 at 11:23:34PM CET: > > /bin/sh ../../../libtool --debug --tag=CC --mode=link arm-mingw32ce-gcc > -g -O2 -no-undefined -Wl,--enable-auto-import -version-info 0:1:0 > -L/home/torri/local/wince/lib -L/home/torri/local/opt/cegcc/lib -o > libdl.la -rpath /home/torri/local/wince/lib libdl_la-dlfcn.lo > ../../../src/lib/libevil.la > libtool_link.txt 2>&1
> + func_lalib_unsafe_p libdl_la-dlfcn.lo > + lalib_p=no > + test -f libdl_la-dlfcn.lo > + test no = yes > + false > + func_fatal_error '`libdl_la-dlfcn.lo'\'' is not a valid libtool object' > + func_error '`libdl_la-dlfcn.lo'\'' is not a valid libtool object' > + echo 'libtool: link: `libdl_la-dlfcn.lo'\'' is not a valid libtool object' > libtool: link: `libdl_la-dlfcn.lo' is not a valid libtool object > + exit 1 This failure is due to some borked file libdl_la-dlfcn.lo, not due to a problem with -lm. Neither the trace nor the config contains -lm anywhere. Maybe you meant a different failure? Cheers, Ralf _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
