Mail Archives: djgpp-workers/1999/08/15/07:13:01
On Fri, 13 Aug 1999, Alain Magloire wrote:
> I've sent autoconf/automake maintainers a patch (see grep-2.3/PATCHES-AC and
> grep-$version/PATCHES-AM)
I found PATCHES-AC in grep-2.3c, but not PATCHES-AM.
> It looks like the new snapshots of autoconf can now cope whti DOS
> environment. I don't follow the in/outs of autoconf, but can we use
> autoconf straight with DJGPP witout doing any funcky sed scripts ?
Perhaps you could try the latest Autoconf and send me the configure
script it creates.
As far as I know, the issues with drive letters in file names are solved
in Autoconf, but the problem with using "test -f" to look for executables
such as gcc is not.
As for Ben's comments about the patches being DJGPP-specific, I think I
disagree. First, the problems with drive letters were solved in latest
Autoconf with similar patches, and they originated from Cygwin and
Mingw32 projects. So, evidently, other environments need them as well.
And second, the "test -x" patch could not be made more general because
GNU standards explicitly forbid using -x, since it is not supported by
some older shells. If there is some more general way of solving the
problem, I'd be glad to hear about it. So far, solutions employed by
DJGPP developers include, apart of the "test -x", the following:
- set GCC in the environment, and disable the offending fragment
altogether.
- use a special environment variable to make "test -f" behave as
"test -x" (this is only available in the latest port of Bash 2.03).
If we can rely on Bash 2.03 being used, then the latter way is probably
better, but it still requires a DJGPP-specific batch file or shell script
to be used to set the variable before `configure' is run.
- Raw text -