This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Should lseek64 be exported?
- To: Andreas Jaeger <aj at suse dot de>
- Subject: Re: Should lseek64 be exported?
- From: "H . J . Lu" <hjl at lucon dot org>
- Date: Thu, 6 Sep 2001 16:27:15 -0700
- Cc: GNU C Library <libc-alpha at sourceware dot cygnus dot com>
- References: <20010906160251.A5531@lucon.org> <u8sndzc3z3.fsf@gromit.moeb>
On Fri, Sep 07, 2001 at 01:08:16AM +0200, Andreas Jaeger wrote:
> "H . J . Lu" <hjl@lucon.org> writes:
>
> > When llseek is used for linking, we get
> >
> > the `llseek' function may be dangerous; use `lseek64' instead.
> >
> > But lseek64 is not exported from libc.so.6.
>
> Please double check:
> gromit:~/ELisp/pgnus:[0]$ nm /lib/libc.so.6 |grep lseek
> 00000000 ? __evoke_link_warning_llseek
> 000c6f70 T __libc_lseek
> 000d3180 T __libc_lseek64
> 000d3180 t __llseek
> 000c6f70 W __lseek
> 000d3180 t __lseek64
> 000d3180 W llseek
> 000c6f70 W lseek
> 000d3180 W lseek64
>
> Why is it not exported for you?
Never mind. I thought it was llseek64.
H.J.