Date: Sun, 18 Aug 1996 15:29:17 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Don Bagert <bagert AT cs DOT coe DOT ttu DOT edu>
Cc: "'djgpp'" <djgpp AT delorie DOT com>
Subject: Re: problem report
In-Reply-To: <3213BF6D@cpds01.coe.ttu.edu>
Message-Id: <Pine.SUN.3.91.960818152601.1338O-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 15 Aug 1996, Don Bagert wrote:

> I have been having a problem with using djgpp.env under gnatlink on a Novell 
> Network server (version 2.15 - yes, I know it's an old version!).  When 
> performing a gnatlink, I receive the following message:
> 
> "f:/lang/gwada/gnat305\bin\ld.exe: cannot open linker script file djgpp.lnk: 
>  No such file or directory (ENOENT)"

This is a known bug in DJGPP v2.0, the latest release 2.01 of the DJGPP 
FAQ describes it thus in section 8.1:

   * Some older versions of Novell Netware cause the linker to fail if the
     libraries or the startup file `crt0.o' reside on a networked drive.
     This is due to a peculiarity of Novell that happens to fail the library
     function `stat' in some cases.  The exact reason of the failure has been
     identified, and the next release of the library will include a version
     of `stat' that works around that problem, so future releases of the
     linker will be free of this bug.  As a temporary work-around, move all
     the libraries and `crt0.o' to a local drive.  (Don't forget to add that
     directory to the `LIBRARY_PATH' line on `DJGPP.ENV.')  Another solution
     would be to upgrade your Novell software; version 4.x is reportedly free
     of this problem.