Re: AC_OBJEXT revisited

[Akim Demaille]

Hi Lars!

| With Autoconf fresh from CVS, two problems occur with the
| OBJEXT test.
| 
| 1) The "test -s conftest.$ac_objext" part of _AC_COMPILE_IFELSE
|    fails because $ac_objext is invalid before the objext test is
|    performed.  This makes configure go the "cannot compute OBJEXT"
|    route which breaks configure.
| 
| Removing that test to get going, reveals the next problem:

Aaarg!  Good point, thanks!

| 2) A "conftest.exe" file is left in $builddir from a previous
|    configure run, causing $ac_objext to be detected as .exe.

Arg again, thanks for pointing this out.

|    `ls' doesn't list the files in the same order as they are
|    written on the command line, causing the priority list to go
|    bonkers, making the .exe file appear before the .obj file.

What kind of ls is that???

|    Maybe this is a better solution: ?
| 
|   m4_define([_AC_COMPILER_OBJEXT],
|   [AC_CACHE_CHECK([for object suffix], ac_cv_objext,
|   [_AC_COMPILE_IFELSE([AC_LANG_PROGRAM()],
| ! [for ac_file in `(ls conftest.o conftest.obj; ls conftest.*) 2>/dev/null`; 
do

That's smart :)  But really, what ls is this???

|     case $ac_file in
|       *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb ) ;;
|       *) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'`
|          break;;
|     esac
|   done],
| 
|   Lars J