Re: when using `which` send errors to /dev/null
On 2007-05-25 12:06:26 -0400, Derek Martin wrote:
> I'm not aware of any Unix-derivative systems where /bin/sh is
> not a Bourne-shell derivative (Bourne Shell, Korn Shell, POSIX shell,
> or Bash). All of those shells use ':' as the path separator for
> $PATH. Can you suggest an example?
It seems that bash can accept/use ';' under some conditions. The
autoconf manual (info) says:
`PATH_SEPARATOR'
If it is not set, `configure' will detect the appropriate path
separator for the build system and set the `PATH_SEPARATOR' output
variable accordingly.
On DJGPP systems, the `PATH_SEPARATOR' environment variable can be
set to either `:' or `;' to control the path separator `bash' uses
to set up certain environment variables (such as `PATH'). Since
this only works inside `bash', you want `configure' to detect the
regular DOS path separator (`;'), so it can be safely substituted
in files that may not support `;' as path separator. So it is
recommended to either unset this variable or set it to `;'.
--
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)