Libtool 1.3.5 comes with it's own poor exe extension test (ltconfig).
The Autoconf macro detects the correct exe-ext, but later when libtool
is being configured, libtool doesn't inherit what configure already
has detected, except if you use a cache file. You're OK with the default
behaviour if you use Autoconf 2.13, but not with the latest CVS Autoconf
in other words.
To make Autoconf's tests override the ltconfig tests, we only need to
export the variable $ac_cv_exeext. I therefore propose the following
patch for CVS Autoconf:
2001-01-11 Lars J. Aas <[EMAIL PROTECTED]>
* aclang.m4 (_AC_COMPILER_EXEEXT_DEFAULT,_AC_COMPILER_EXEEXT_O):
Export ac_cv_exeext to environment to override incorrect exeext
test in ltconfig from libtool-1.3.5.
Index: aclang.m4
===================================================================
RCS file: /cvs/autoconf/aclang.m4,v
retrieving revision 1.106
diff -u -r1.106 aclang.m4
--- aclang.m4 2001/01/11 15:17:13 1.106
+++ aclang.m4 2001/01/11 17:23:49
@@ -659,6 +659,7 @@
case $ac_file in
*.$ac_ext | *.out | *.o | *.obj | *.xcoff | *.tds | *.d | *.pdb ) ;;
*) ac_cv_exeext=`expr "$ac_file" : ['[^.]*\(\..*\)']`
+ export ac_cv_exeext
break;;
esac
done],
@@ -684,6 +685,7 @@
case $ac_file in
*.$ac_ext | *.o | *.obj | *.xcoff | *.tds | *.d | *.pdb ) ;;
*) ac_cv_exeext=`expr "$ac_file" : ['[^.]*\(\..*\)']`
+ export ac_cv_exeext
break;;
esac
done],
