On Thu, 2002-02-14 at 15:49, John Poltorak wrote: > On Thu, Feb 14, 2002 at 03:07:41PM +0100, Tim Van Holder wrote: > > On Thu, 2002-02-14 at 14:09, John Poltorak wrote: > > > On Thu, Feb 14, 2002 at 01:31:06PM +0100, Tim Van Holder wrote: > > > > > > Yes, I have this line (with -E) in config.site, but config.log shows:- > > > > > > > > > PATH: c:\us in > > > PATH: c:\emx in > > > PATH: c:\usr\loca in > > > PATH: c:\os2 > > > PATH: . > > > > Probably because this is logged before config.site is run. > > Again I must point out that the behaviour of ksh's echo could be > > considered broken; it requires an option to behave 'normally'. > > Is there a definitive view on this? > > The OS/2 porter of KSH considers that the default mode for ECHO should be > to interpret escape characters rather than ignore them.
Understood. It's not really relevant to the discussion at hand anyway; all I really meant was that autoconf tends to expect a Bourne shell (i.e. sh, ash, bash). It is no longer a hard requirement (I think it used to be in 2.13), but the escape-expansion used by ksh, zsh, csh, ... still has the potential of messing things up. > Yes, I have an envvar pointing to CONFIG_SITE, but any variables which it > sets are not applicable to autoconf. What would be useful would be to have > autoconf reading config.site as well. As I said before, autoconf is a Perl script, so config.site is irrelevant there. Perl is supposed to handle PATH properly though. Why exactly do you want autoconf itself to read config.site?
