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: Mon, 08 Dec 2003 19:43:32 -0500 Message-ID: <696atv4an5pmt7ptq7gc94j29cpc88mbks@4ax.com> References: <9fa9tvceuioq08dj7gqv29vn8ui939mi2d AT 4ax DOT com> In-Reply-To: <9fa9tvceuioq08dj7gqv29vn8ui939mi2d@4ax.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On Mon, 08 Dec 2003 11:51:48 -0500, I wrote: >To the Cygwin mailing list: > >Back in January, Thomas Baker (who is BCC'd on this) posted a question >about a large call to cp giving an error message about not being able >to create a hard link. Ref: >. > >I've just upgraded cygwin from 1.3.22-1 (March 18, 2003) to a couple >of different 1.5.x versions, including 1.5.5-1 (Sept 20, 2003), and >have started getting this error. > >It happens in a build script that is copying about 30 directories that >contain around 3000 files in total. > >Does anyone know what's going wrong here, or any workarounds other >than "don't upgrade"? 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. 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/