From: Thomas Demmer Newsgroups: comp.os.msdos.djgpp Subject: Re: LD looks at zip drive Date: Tue, 30 Dec 1997 08:41:10 +0100 Organization: Lehrstuhl fuer Stroemungsmechanik Lines: 31 Message-ID: <34A8A596.1F44B711@LSTM.Ruhr-UNI-Bochum.De> References: <3481D587 DOT 5A03 AT netunlimited DOT net> <19971229043201 DOT XAA20808 AT ladder01 DOT news DOT aol DOT com> <687t62$7h2 AT freenet-news DOT carleton DOT ca> <34a87317 DOT 0 AT 204 DOT 101 DOT 95 DOT 15> NNTP-Posting-Host: bvb.lstm.ruhr-uni-bochum.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Colin Walsh wrote: [...] > > My zip drive (which I've only had for a few days) does the same exact thing > when I compile (and I'm not using RHIDE). I put the -v switch in and it occurs > when ld is running. In the command line used to invoke ld there is no reference > to any files being accessed on drive d:, also, there is no reference to anything > on the drive in my path. I'm guessing tho' that no harm is being done and its > just some sort of quirk of ld. If I recall correctly, ld performs some stat()ing of the library path, to see if it is contains symbolic links and other Unix'y issues. So stat() has to check if some drives exist, or if they are mapped to network drives. Much the same will happen to you if you run df to find out some information about your drives. Eli can probably tell you a lot more of the guts of stat() and when this effect happens. -- Ciao Tom ************************************************************* * Thomas Demmer * * Lehrstuhl fuer Stroemungsmechanik * * Ruhr-Uni-Bochum * * Universitaetsstr. 150 * * D-44780 Bochum * * Tel: +49 234 700 6434 * * Fax: +49 234 709 4162 * * http://www.lstm.ruhr-uni-bochum.de/~demmer * *************************************************************