From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: this adds lseek64 to klibc
Date: Thu, 15 Jul 2004 15:50:09 +0000 [thread overview]
Message-ID: <40F6A7B1.20401@zytor.com> (raw)
In-Reply-To: <40F649B0.6020201@redhat.com>
Harald Hoyer wrote:
> +#define lseek64 llseek
>
>
> ------------------------------------------------------------------------
>
> diff -ur udev-029/klibc/klibc/include/unistd.h udev-029.new/klibc/klibc/include/unistd.h
> --- udev-029/klibc/klibc/include/unistd.h 2004-07-02 20:17:03.000000000 +0200
> +++ udev-029.new/klibc/klibc/include/unistd.h 2004-07-06 15:11:05.144770448 +0200
> @@ -83,6 +83,7 @@
> __extern int close(int);
> __extern off_t lseek(int, off_t, int);
> __extern loff_t llseek(int, loff_t, int);
> +#define lseek64 llseek
> __extern int dup(int);
> __extern int dup2(int, int);
> __extern int fcntl(int, int, long);
>
What is this for? I'm not supporting the rest of the *64() functions,
or rather, they're implicit as if you compiled with
-D_FILE_OFFSET_BITSd on glibc; adding just one (and as a define, too!)
is ugly.
-hpa
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idG21&alloc_id\x10040&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-07-15 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 9:09 this adds lseek64 to klibc Harald Hoyer
2004-07-15 15:50 ` H. Peter Anvin [this message]
2004-07-15 17:37 ` Harald Hoyer
2004-07-15 17:41 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40F6A7B1.20401@zytor.com \
--to=hpa@zytor.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).