Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 12 Apr 2005 19:44:32 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin coreutils-5.3.0-4 rm change breaks Libtool Message-ID: <20050412234432.GA17857@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <041220052251.26916.425C50E800071C000000692422007507840A050E040D0C079D0A@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <041220052251.26916.425C50E800071C000000692422007507840A050E040D0C079D0A@comcast.net> User-Agent: Mutt/1.5.8i On Tue, Apr 12, 2005 at 10:51:20PM +0000, Eric Blake wrote: >To some degree, the problem isn't even coreutils fault - cygwin itself >is where it was decided that stat(2) succeeds for either "foo" or >"foo.exe" when only "foo.exe" exists, but that unlink(2) fails unless >it is spelled "foo.exe". The implicit .exe magic I added in rm is >simply recognizing that if stat succeeded but unlink failed, that >unlink should be tried a second time with the correct extension. I'm not sure I understand this. If cygwin were made to not treat .exe specially, that would mean that, presumably, either you'd remove all of your patches from coreutils and make people use .exe specifically, or you would work around the lack of .exe by adding it on your own. If you wanted to just make people always have to specify .exe then you probably should have just introduced a simple wrapper around stat which defeated cygwin's attempt to detect .exe's. cgf -- 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/