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 To: Doru Carastan Cc: cygwin@cygwin.com Subject: Re: .exe handling change in fileutils-4.1-2 References: <3FB520C6.5030807@mvista.com> From: "Nathan J. Williams" Organization: Wasabi Systems, Inc. Date: 14 Nov 2003 13:45:23 -0500 In-Reply-To: <3FB520C6.5030807@mvista.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Doru Carastan writes: > In reply to: http://cygwin.com/ml/cygwin/2003-11/msg00478.html > -------------------------------------------------------------- > > It is normal to see "touch foo.exe; cp foo bar" fail. You just created > foo.exe, which is definitely not foo. Check with "ls -l". Yes, I'm aware that foo.exe is not foo, but fileutils-4.1-1 contained code which special-cased this situation, IMO very usefully. What I would like to see is a ChangeLog entry or CVS log message or something that corresponds to and explains the removal of that code. > The current versions of autoconf and automake define and use > EXEEXT=.exe. Check your Makefile.am or Makefile.in files and add > $(EXEEXT) to all commands that involve executables. The build system in question is not based on autoconf/automake. - Nathan -- 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/