Gary V. Vaughan writes:
> The attached files are FYI, and represent the commits I made to HEAD.
> + yes,cygwin*)
> + library_names_spec='`echo ${libname} | sed -e 's/^lib/cyg/'``echo ${release} |
>[sed -e 's/[.]/-/g']`${versuffix}.dll'
> + ;;
> + 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"`
> + ;;
> + yes,pw32*)
> + library_names_spec='`echo ${libname} | sed -e 's/^lib/pw/'``echo ${release} |
>sed -e 's/[.]/-/g'`${versuffix}.dll'
> + ;;
Some of what looks like spaces at the start of those added lines are
actually Latin-1 NBSP characters (\240)... Ouch! I spent half an hour
wondering why bash had suddenly started acting like crazy, the case
statement didn't match the yes,mingw*) case even though I had GCC=yes
and host_os=mingw32... I wonder where those \240 chars came from?
--tml
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool