Message-Id: <5.0.2.1.0.20001227141202.025ac6b0@pop5.banet.net> X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Wed, 27 Dec 2000 14:17:36 -0500 To: Eli Zaretskii From: "Peter J. Farley III" Subject: Re: llseek is not in stubs.h (was: Re: Locking fcntl changes #2) Cc: djgpp-workers AT delorie DOT com In-Reply-To: References: <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001227015917 DOT 00a83050 AT pop5 DOT banet DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk At 10:11 AM 12/27/00 +0200, Eli Zaretskii wrote: >If you call llseek inside fcntl, then you indeed need to add it to >stubs.h. > >Note that you don't need to change the name of llseek in llseek.c (or >whatever its source is called): just #include in it, and >it will do it for you. Including stubs.h is the only thing you need to >do on the source level. Let me understand this correctly -- just include in fcntl.c (where it is used) and the make process will automatically add it to a newly created version of libc/stubs.h, is that right? Or is it llseek.c that needs the include for ? I'm confused because *both* fcntl.c and llseek.c currently include , and llseek has *not* been generated into stubs.h in the many makes I have run. --------------------------------------------------------- Peter J. Farley III (pjfarley AT dorsai DOT org OR pjfarley AT banet DOT net)