autoconf and OS/2

[Andreas Büning]

Hello!

I had problems with a configure script using OS/2. There were
two problems:

1) *.exe files weren't found in $PATH
2) configure terminated after trying to create a link

My patches (autoconf 2.50):

1)

$diff /temp/autoconf-2.50/m4sh.m4 m4sh.m4
419c419,436
< [as_executable_p="test -f"
---
> [_as_executable_p="test -f"
> function_find_executable()
> { if test -z "$SYSTEM_HAS_EXE_SUFFIX_TESTED"; then
>     SYSTEM_HAS_EXE_SUFFIX_TESTED="1"
>     # if there is ls.exe then ".exe" should be an executable extension
>     if ls.exe -a "*" >/dev/null 2>/dev/null; then
>       SYSTEM_HAS_EXE_SUFFIX=".exe"
>     else
>       SYSTEM_HAS_EXE_SUFFIX=
>     fi
>   fi
>   if $_as_executable_p translit(`$A*', `A'); then return 0; fi
>   if test -n "$SYSTEM_HAS_EXE_SUFFIX"; then
>     if $_as_executable_p translit(`$A*', `A')"$SYSTEM_HAS_EXE_SUFFIX"; then 
> return 0; fi
>   fi
>   return 1;
> }
> as_executable_p=function_find_executable


2)

$diff /temp/autoconf-2.50/acgeneral.m4 acgeneral.m4
4386c4386,4387
<     AC_MSG_ERROR([cannot link $ac_dest to $srcdir/$ac_source])
---
>       (cp -p $srcdir/$ac_source $ac_dest &&
>         AC_MSG_WARN([cannot link $ac_dest to $srcdir/$ac_source, using cp -p 
> instead]))


I'm not familiar with autoconf, so if this code isn't convenient to you, 
don't bash me! ;-) However, it works for me, at least with OS/2 and
Linux.
(autoconf itself does not run with OS/2, but the configure script does)

There is another thing. The configure scripts don't find any executable
if there are only backslashes instead of forward slahes in $PATH. If
possible,
could you add a check either to convert '\\' into '/' or a at least to
print a warning, if there are no forward slashes at all in $PATH? Then a
user
would know, what's the problem.


bye,
Andreas