X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 7 May 2008 15:26:23 +0300 (EEST) From: tommi DOT sairo AT elisanet DOT fi Reply-To: tommi DOT sairo AT iki DOT fi To: cygwin AT cygwin DOT com Message-ID: <9247911.266331210163183588.JavaMail.tommi.sairo@elisanet.fi> Subject: tar failing hard link creation MIME-Version: 1.0 Content-Type: text/plain; Charset=iso-8859-1; Format=Flowed Content-Transfer-Encoding: 7bit X-Mailer: Saunalahti webmail - http://saunalahti.fi Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Hi, There is something mysterious in tar with Cygwin when archive contains hard links. Similar issues have been reported earlier: http://sourceware.org/ml/cygwin/2006-12/msg00251.html http://sourceware.org/ml/cygwin/2007-01/msg00705.html In my case, a colleague was trying to extract a pre-built cross-toolchain on his brand new WinXP laptop from a tarball I had created earlier. This tarball extracts just fine on all tried systems except this one. Cygwin setup is exactly the same as in other computers (installed from same set of packages burnt on CD-R). Cygwin root is on NTFS filesystem. Creating hard links manually using ln works fine, but tar cannot extract hard links from an archive, giving errors like: tar: bar: Cannot hard link to 'foo': File exists Updating to current tar (1.20) gives the exact same behavior, but made it possible to circumvent the problem by repackaging the files with the new --hard-dereference option. /TS -- 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/