Mail Archives: djgpp-workers/2001/04/11/14:54:53
> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Wed, 11 Apr 2001 19:01:19 +0200
>
> An AC_SUBST for a pathsep was very desirable, as it allows files (such
> as, in the case of autoconf, the test harness) to use the correct pathsep
> for the system.
This is not required by DJGPP. Our Bash will do the right thing both
with ':' and with ';', provided that the configure script and
PATH_SEPARATOR are consistent. That is, if the configure script uses
';' and PATH_SEPARATOR is ';', the script will work, and the same for
':'.
> It's also very useful for typical Makefile's that build manuals; they tend
> to set TEXINPUTS (using a ':' as separator). Now such Makefile.in's can
> use @PATH_SEPARATOR@ instead and get the correct pathsep at configure time.
This is indeed a welcome change, one that I was talking with varuious
maintainers about for a long time. But it doesn't need to use the
same variable name. In fact, it better not use PATH_SEPARATOR,
because it is quite possible that some scripts which are run by Make
do not honor PATH_SEPARATOR and still rely on ':' without testing.
This is the breakage that I'm afraid of.
> Come to think of it, how likely is it for external, :-using scripts to
> be run during configure?
I don't know. Lately, we see new scripts popping up both during
configure time and build time. libtool and depcomp are two notable
examples. I think it would be good to not have to change the
DJGPP-specific files and ports each time a new script is born.
- Raw text -