Re: autoconf and OS/2

[Tim Van Holder]

> > variables (and undocumented ones as well); with the
> > ac_executable_extensions patch, you could simply do
> > 
> > set ac_executable_extensions=".exe .bat .cmd"
> > sh configure
> > 
> > and it would work (without relying on --prefix).
> 
> And I'd like to see this patch in the official distribution.
So would I - Akim, your final words on this?  I agree that perhaps
a different solution is needed in the long run, but having this
ability in 2.51 would help platforms like DJGPP and OS/2 _now_.

> In my opinion it would be sufficient to test if there are any (forward)
> slashes in $PATH and to print a warning if there isn't a slash.
> Then the user knows what he has to do.

Hmm - not sure about that one.  Backslashes in PATH _should_ work
though:

[configure.ac]
AC_INIT
AC_PATH_PROG(GCC, gcc)
AC_PATH_PROG(ABC, abc)
PATH=`echo $PATH | tr '/' '\\\\'`
AC_PATH_PROG(PERL, perl)
AC_OUTPUT

[output]
configure: loading site script /dev/env/DJDIR/share/config.site
checking for gcc... /dev/env/DJDIR/bin/gcc.exe
checking for abc... no
checking for perl... E:\Djgpp\Bin/perl.exe
configure: creating ./config.status

My guess is that your system simply does not support forward slashes
in paths at all, so when configure tries to see if C:\EMX\BIN/gcc.exe
exists, it fails.  Could you try the above configure.ac and see what
it prints on OS/2?
Also, try 'test -f c:/some/dir/file-that-exists && echo Yippie' in
your shell - does that print 'Yippie' like it should?
I'm not sure we want to have an ac_dirsep for this purpose though.