Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <38FF79D4.7E054C75@vinschen.de>
Date: Thu, 20 Apr 2000 23:42:44 +0200
From: Corinna Vinschen <corinna AT vinschen DOT de>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language: de, en
MIME-Version: 1.0
CC: cygwin AT sourceware DOT cygnus DOT com
Subject: link call patched [was Re: broken 'ln' behavior -Reply]
References: <s8fc30b4 DOT 079 AT rwdi DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


FYI, I have patched the link(2) call in cygwin1.dll so that paths
are checked if they have a trailing slash. In that case, link()
bails out now with EINVAL.

This patch will be part of the tomorrows snapshot.

Corinna

Chris Portaix wrote:
> I've had this same problem using shell scripts (csh, tcsh, sh and bash)
> on cygwin; they do not recognize these links. So I modofeid them to cp
> insteat of ln. It's a temporary solution cause things can get tricky with cp.
> regards,
> Chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com