Message-Id: <5.0.2.1.0.20001227015917.00a83050@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Wed, 27 Dec 2000 02:09:29 -0500
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: llseek is not in stubs.h (was: Re: Locking fcntl changes #2)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <200012171037.LAA13861@father.ludd.luth.se>
References: <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001217024611 DOT 025a3680 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 11:37 AM 12/17/00 +0100, Martin Str|mberg wrote:
 >According to Peter J. Farley III:
 >> Well, in this case we already had a POSIX function, fcntl, calling 
a
 >> non-ANSI function, filelength, which is why I would then presume 
that
 >> the #define for filelength was *already* in stubs.h.  Since fcntl
 >> will now be calling lfilelength, doesn't the same rationale apply 
for
 >> the location of a define for lfilelength?
 >
 >Please verify that llseek() is there too. (I suspect not.)

It is not.  llseek is only defined in the non-POSIX section of 
include/unistd.h, and nowhere else.

Should llseek be following the example of filelength, being defined as 
__llseek and having a "#define llseek __llseek" in 
include/libc/stubs.h?  Or what, keeping in mind that my new fcntl is 
the first libc function to internally use llseek, and that fcntl is 
POSIX?

---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)