Date: Thu, 12 Jun 1997 13:27:17 +0200
From: Teun Burgers <burgers AT ecn DOT nl>
Subject: Re: Help building Libc from source
To: peterm AT zip DOT com DOT au
Cc: djgpp AT delorie DOT com
Message-id: <9706121127.AA31163@joost.ecn.nl>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Content-MD5: B//WSFZgNUX5Oak+17dHVg==
Precedence: bulk

> From dj-admin AT delorie DOT com Thu Jun 12 13:08:07 1997
> Subject: Help building Libc from source
> To: djgpp AT delorie DOT com
Hello Peter,

I once had a problem with the _rename call from libc also in
combination with a networked drive.

When debugging _rename.c it was not necessary to rebuild the entire
libc. When you compile

gcc -o _rename -DTEST _rename.c

you get an executable. You can modify and test/debug this small program
easily. Perhaps the same method works for your problem as well.

Teun Burgers

> Hi,
> I am trying to debug a problem with cp, bash(b9) and my network
> configuration (BTW, cp works fine with 4DOS and cp :-)). I have gotten
> down to the problem possibly being in the open call to open the
> destination file. But when I unzip djlsr201 and try and compile the
> source for libc I get an assembly error in the longjump.s file. I have
> downloaded the following (minimal) subset and get the same problem:
> 
> bnu27b
> djdev201
> gcc2721b
> gpp2721b
> mak375b
> 
> Any ideas? BTW, I am running Win95 and a network that has HummingBirds
> TCP/IP stack onto a Sun fileserver runing PC-NFS.
> 
> Thanks
> 
> Peter