Date: Tue, 16 Mar 1999 14:53:43 -0500
Message-Id: <199903161953.OAA20461@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <199903161751.RAA53418@out5.ibm.net> (snowball3@usa.net)
Subject: Re: symlink question
References:  <199903161751 DOT RAA53418 AT out5 DOT ibm DOT net>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> > Even if x or x.exe don't exist, y.exe is still generated. Is this behavior
> >  correct?
> 
> Let me change question. Should this behavior continue to be 
> supported? Autoconf generated configure scripts uses a non-existant 
> file to check for 'ln -s' support. Since 'ln -s' works only in special 
> circumstances, it might be a good idea allow symlink() or at least 'ln -s' 
> to fail for non-existant files.

"ln -s" should succeed in djgpp whenever it succeeds in Linux.  You
can symlink to a non-existing file in Linux.

"ls" (no -s) should fail if the source doesn't exist.