Date:	Wed, 27 Dec 2000 14:50:58 -0500
Message-Id:	<200012271950.OAA04054@envy.delorie.com>
X-Authentication-Warning:	envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp-workers AT delorie DOT com
CC:	eliz AT is DOT elta DOT co DOT il, djgpp-workers AT delorie DOT com
In-reply-to:	<5.0.2.1.0.20001227141202.025ac6b0@pop5.banet.net>
	(pjfarley AT banet DOT net)
Subject:	Re: llseek is not in stubs.h (was: Re: Locking fcntl changes
	#2)
References:	<5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001227015917 DOT 00a83050 AT pop5 DOT banet DOT net> <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001227141202 DOT 025ac6b0 AT pop5 DOT banet DOT net>
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

> Let me understand this correctly -- just include <libc/stubs.h> 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 <libc/stubs.h>?

You include stubs.h in any source that defines functions that end up
stubbed, *and* in any sources that need to use stubbed functions.
It's safe to include it when not needed.

> I'm confused because *both* fcntl.c and llseek.c currently include 
> <libc/stubs.h>, and llseek has *not* been generated into stubs.h in the 
> many makes I have run.

stubs.h has to be edited manually to add new entries.  Once llseek()
is added to the list, then fcntl.c uses stubs.h to call __llseek()
instead of llseek(), and llseek.c uses it to redefine the function to
be __llseek().  The src/libc/stubs makefile builds a llseek function
that just jumps to __llseek.

- Raw text -