Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	ericblake AT comcast DOT net (Eric Blake)
To:	cygwin AT cygwin DOT com
Subject:	Re: Coreutils (ln) bugs
Date:	Thu, 23 Jun 2005 17:08:27 +0000
Message-Id:	<062320051708.22933.42BAEC8B00015F860000599522007510900A050E040D0C079D0A@comcast.net>
X-Authenticated-Sender:	ZXJpY2JsYWtlQGNvbWNhc3QubmV0

> Bug 1:
> $ ln foo bar
> where the real name is foo.exe
> works ok, but erroneously returns exit status 1

Thanks for the report.  It is even weirder than that - if foo.exe is not executable, it complains:
$ touch abc.exe
$ ln abc 123
ln: creating hard link `123' to `abc': No such file or directory
$ echo $?
1
$ ls abc* 123*
ls: 123*: No such file or directory
abc.exe

I'll add this to my list of issues to resolve before letting coreutils-5.3.0-7 out the door (I'm hoping to have enough time to get it released by the end of next week).

--
Eric Blake
cygwin coreutils maintainer



--
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/

- Raw text -