RE: new libtool.m4 patch for cygwin & mingw

[Kevin Wright]

Tor,

>From the README.txt in the bzipped version of Edwards libtool-cygwin:

 PPS. Really smart cookies will notice a seemingly nonsensical diff in
 the patch file. That's because someone committed some file(s) into
 cvs with embedded binary characters. I have no idea what they were,
 but I removed them. Maybe a foreign character set. Who knows?

Perhaps this explains the problem.

--Kevin

> -----Original Message-----
> From: address@hidden [mailto:address@hidden Behalf Of
> Tor Lillqvist
> Sent: Thursday, March 08, 2001 2:39 PM
> To: Gary V. Vaughan
> Cc: Tor Lillqvist; Stefan Ondrejicka; address@hidden
> Subject: Re: new libtool.m4 patch for cygwin & mingw
>
>
> 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
> address@hidden
> http://mail.gnu.org/mailman/listinfo/libtool
>