libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new libtool.m4 patch for cygwin & mingw


From: Tor Lillqvist
Subject: Re: new libtool.m4 patch for cygwin & mingw
Date: Fri, 9 Mar 2001 00:39:17 +0200 (FLE Standard Time)

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]