"Gary V. Vaughan" wrote:
>
> On Sat, Sep 22, 2001 at 11:15:43PM +0300, Tor Lillqvist wrote:
> > The chance of a Unix system having
> > directory names containing semicolons is practically nil, isn't it?
>
> Yup. It is possible technically, but anyone who uses semicolons in
> PATH has got to expect trouble, no?
>
I think we agree. Now, I wonder if we would be so frank to just
nuke the $path_separator thing and just go over to use *only*
this generic heuristic about ';' occuring pathnames.
Here's an example patch on top of libtool-1-4 ... which has the
original code before we started to mess around with $path_separator.
Otherwise it would again be needed to ensure path_separator is set.
(the 1-4 lt_cv_sys_path_separator is always ':' but on djgpp)
for the 1-5 branch, we do make some assumptions about the help of
autoconf anyway IIRC, but again we might just go and use the
generic path_seperator detection for sys_lib_search_path as well.
WDYT?
cheers, guido
Index: libtool.m4
===================================================================
RCS file: /cvsroot/libtool/libtool/libtool.m4,v
retrieving revision 1.166.2.28
diff -u -r1.166.2.28 libtool.m4
--- libtool.m4 2001/09/21 18:09:59 1.166.2.28
+++ libtool.m4 2001/09/23 15:27:47
@@ -2033,7 +2033,11 @@
;;
yes,mingw*)
library_names_spec='${libname}`echo ${release} | sed -e
's/[[.]]/-/g'`${versuffix}.dll'
- sys_lib_search_path_spec=`$CC -print-search-dirs | grep "^libraries:" | sed -e
"s/^libraries://" -e "s/;/ /g"`
+ sys_lib_search_path_spec=`$CC -print-search-dirs | grep "^libraries:" | sed -e
+"s/^libraries://"`
+ if echo $sys_lib_search_path_spec | grep ';' >/dev/null
+ then sys_lib_search_path_spec=`echo $sys_lib_search_path_spec | sed -e "s/;/ /g"`
+ else sys_lib_search_path_spec=`echo $sys_lib_search_path_spec | sed -e "s/:/ /g"`
+ fi
;;
yes,pw32*)
library_names_spec='`echo ${libname} | sed -e 's/^lib/pw/'``echo ${release} | sed
-e 's/[.]/-/g'`${versuffix}.dll'
