From e09d62bc198ba01db8de04885a24eb43dc203266 Mon Sep 17 00:00:00 2001 From: Ralf Wildenhues Date: Tue, 23 Jan 2007 18:47:23 +0000 Subject: [PATCH] * doc/autoconf.texi (File System Conventions): Mention that $PATH_SEPARATOR is for the build system only. Report by Keith Marshall. --- ChangeLog | 6 ++++++ doc/autoconf.texi | 3 ++- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/ChangeLog b/ChangeLog index c97ea01d..112119d0 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2007-01-23 Ralf Wildenhues + + * doc/autoconf.texi (File System Conventions): Mention that + $PATH_SEPARATOR is for the build system only. + Report by Keith Marshall. + 2007-01-19 Ralf Wildenhues * doc/autoconf.texi (Setting Output Variables): Mention that diff --git a/doc/autoconf.texi b/doc/autoconf.texi index b56c2f91..9d7291e3 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -11399,7 +11399,8 @@ first character (@pxref{Limitations of Builtins}). Also, because the colon is used as part of a drivespec, these systems don't use it as path separator. When creating or accessing paths, you can use the @code{PATH_SEPARATOR} output variable instead. @command{configure} sets this -to the appropriate value (@samp{:} or @samp{;}) when it starts up. +to the appropriate value for the build system (@samp{:} or @samp{;}) when it +starts up. File names need extra care as well. While @acronym{DOS} variants that are Posixy enough to run @command{autoconf} (such as @acronym{DJGPP}) -- 2.47.2