-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Charles Wilson on 4/12/2005 7:33 PM: > Eric Blake wrote: > >> Which line? Since you already found the culprit, pointing others to >> the location would be helpful. Can you come up with a simple libtool >> patch? > > > I know where. Actually, I'd prefer to keep the rm, if there is a > mechanism to say "rm foo but NOT foo.exe". Does the "rm -f foo." trick > still work to specify "foo without any extension and I really mean it."
Yes, it still works on normal mounts, since Windows strips all trailing dots and spaces, and cygwin does not do automatic extension adding if the command line has a trailing dot. However, on managed mounts, q. is a valid filename, so `rm -f q.' silently fails rather than removing the script, and if q. and q.exe exist in the managed mount, invoking plain q gets q.exe and not the script `q.'. And since some packages have non-portable file names requiring the use of a managed mount to unpack them, it could get difficult to relibtoolize such a package if libtool uses the trailing dot trick. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCXHqg84KuGfSFAYARAhKVAKCI6VLigU/FHSwjazQ6dlwgFc9vfgCeMoX0 OawCIcJloKrsiYZHu89TT5s= =0S2y -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
