Re: autoconf and OS/2

[Andreas Buening]

Tim Van Holder wrote:
> 
> > In my opinion a additional configure option would be the best solution
> > (or a documented environment variable if you like). Why? It doesn't
> 
> Well, config.site is merely a way to set such documented evironment
> 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.


[snip]

> Yes, but
>   a) most systems that use \ also support / (DJGPP, Cygwin)
>   b) checking \ requires quoting the \ properly, which is harder
>      if it's in a variable that might just have a / - so [\\/] is used
>      wherever it's needed.  This is not optimal (a Unix path with an
>      embedded backslash won't work properly), but it's probably the best
>      we can do.  I will try to look into the PATH issue at some point in
>      the near future, but I would recommend using a config.site and
>      massaging $PATH there yourself.

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.


bye,
Andreas