Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	"Dr. Wayne Keen" <wayne DOT keen AT crc DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	Re: problem with the link command : ln
Date:	Tue, 9 Jul 2002 08:06:49 -0400
Message-ID:	<000601c22741$1a984720$a701a8c0@earthlink.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4807.1700

> Check if you have multiple copies of cygwin1.dll, and see if have
> any aliases or scripts also named 'ln' that might be executed instead
> of /bin/ln.exe.

This is a good point.  One of the first steps when a command seems to
be having problems is to do a which on the command to find out
where it is coming from, i.e.

which ln 

that in my case returns

/usr/bin/ln

See my post from a earlier today about multiple copies of cygwin1.dll.
I thought I was pretty smart about that, but I found an application,
ds9, had put not one, but maybe two different versions of cygwin1.dll
on my system.

Wayne Keen

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -