Date: Mon, 30 Mar 1998 14:14:07 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Eric Gillespie <viking AT flying-brick DOT caverock DOT co DOT nz>
cc: djgpp AT delorie DOT com
Subject: Re: Can't Get GCC 2.8.0 to build?
In-Reply-To: <351ec412.flying-brick@flying-brick.caverock.net.nz>
Message-ID: <Pine.SUN.3.91.980330141159.19525L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 30 Mar 1998, Eric Gillespie wrote:

>      brick:/$ ln -s /usr/root/doglearn.txt doggie.txt
>      f:/djgpp/bin/ln: cannot create symbolic link `doggie.txt' to
>         `/usr/root/doglearn.txt': Improper link (EXDEV)
> 
> And when I tried it in the SAME directory as the file concerned, I got:
> 
>       brick:~$ ln -s /usr/root/doglearn.txt doggie.txt
>       brick:~$
> 
> i.e. it worked, but instead of doggie.txt I got a doggie.exe instead (2048 
> bytes, just the right size for the stub!)

I really don't understand why did you need to run all those tests: it is 
all described in the README file which comes with the DJGPP port of GNU 
Fileutils (that's where `ln' program comes from).