Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-pair-Authenticated: 65.93.68.37 From: Duncan Murdoch To: cygwin AT cygwin DOT com Subject: Re: "cp: will not create hard link" Date: Tue, 09 Dec 2003 19:26:12 -0500 Message-ID: References: <9fa9tvceuioq08dj7gqv29vn8ui939mi2d AT 4ax DOT com> <696atv4an5pmt7ptq7gc94j29cpc88mbks AT 4ax DOT com> <20031209011850 DOT GB12260 AT redhat DOT com> <6haatvoo9u4mh78eem9vhpnnsrn5pp1vfq AT 4ax DOT com> In-Reply-To: <6haatvoo9u4mh78eem9vhpnnsrn5pp1vfq@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On Mon, 08 Dec 2003 21:57:07 -0500, you wrote: >On Mon, 8 Dec 2003 20:18:50 -0500, you wrote: > >>On Mon, Dec 08, 2003 at 07:43:32PM -0500, Duncan Murdoch wrote: >>>I think I've tracked this down. My path contained an old version of >>>cp.exe, ahead of the newly installed one. It must have been >>>incompatible with the newly installed cygwin dll. >> >>It doesn't work that way. New dlls always work with older binaries. >>If this "cp" was a cygwin binary then it would work. > >Well, it didn't. Renaming the old cp.exe to get it out of the way >made the build script continue on and die a bit later (when it got to >an old version of find.exe). Just noticed that this doesn't really prove that it's the new Cygwin that is incompatible. Here's more detail: These combinations work: old cp.exe with Cygwin 1.3.22-1 new cp.exe with Cygwin 1.5.5-1 This doesn't: old cp.exe with Cygwin 1.5.5-1 I'm not completely sure of the origin of the old cp.exe, but I think it's from fileutils-4.1-1. It's dated June 15, 2001. It's definitely importing things from cygwin1.dll. Duncan Murdoch -- 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/