From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix IA-64 build
Date: Sun, 04 Aug 2002 15:28:00 -0000 [thread overview]
Message-ID: <20020805002818.V20867@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <20020804235304.U20867@sunsite.ms.mff.cuni.cz>; from jakub@redhat.com on Sun, Aug 04, 2002 at 11:53:04PM +0200
On Sun, Aug 04, 2002 at 11:53:04PM +0200, Jakub Jelinek wrote:
> IA-64 doesn't build either (even with this patch), will look into it tomorrow morning.
I believe this should fix it (bootstrap pending).
__lseek was defined in both lseek.os and llseek.os (and __llseek nowhere).
2002-08-05 Jakub Jelinek <jakub@redhat.com>
* sysdeps/unix/sysv/linux/ia64/syscalls.list (llseek): Provide
__llseek alias, not __lseek.
* sysdeps/unix/sysv/linux/s390/s390-64/syscalls.list (llseek):
Likewise.
* manual/debug.texi (%MENU%): Remove trailing dot.
Reported by <hayastan132@hotmail.com>.
--- libc/manual/debug.texi.jj 2002-08-04 21:57:15.000000000 +0200
+++ libc/manual/debug.texi 2002-08-05 00:41:19.000000000 +0200
@@ -1,6 +1,6 @@
@node Debugging Support
@c @node Debugging Support, , Cryptographic Functions, Top
-@c %MENU% Functions to help debugging applications.
+@c %MENU% Functions to help debugging applications
@chapter Debugging support
Applications are usually debugged using dedicated debugger programs.
--- libc/sysdeps/unix/sysv/linux/ia64/syscalls.list.jj 2002-08-04 20:23:28.000000000 +0200
+++ libc/sysdeps/unix/sysv/linux/ia64/syscalls.list 2002-08-05 00:40:02.000000000 +0200
@@ -3,7 +3,7 @@
umount2 - umount 2 __umount2 umount2
# Whee! 64-bit systems naturally implement llseek.
-llseek EXTRA lseek 3 __libc_lseek64 __lseek llseek __lseek64 lseek64
+llseek EXTRA lseek 3 __libc_lseek64 __llseek llseek __lseek64 lseek64
pread - pread 4 __libc_pread __libc_pread64 __pread pread __pread64 pread64
pwrite - pwrite 4 __libc_pwrite __libc_pwrite64 __pwrite pwrite __pwrite64 pwrite64
fstatfs - fstatfs i:ip __fstatfs fstatfs fstatfs64 __fstatfs64
--- libc/sysdeps/unix/sysv/linux/s390/s390-64/syscalls.list.jj 2002-08-04 20:23:28.000000000 +0200
+++ libc/sysdeps/unix/sysv/linux/s390/s390-64/syscalls.list 2002-08-05 00:40:37.000000000 +0200
@@ -1,6 +1,6 @@
# File name Caller Syscall name # args Strong name Weak names
-llseek EXTRA lseek 3 __libc_lseek64 __lseek llseek __lseek64 lseek64
+llseek EXTRA lseek 3 __libc_lseek64 __llseek llseek __lseek64 lseek64
pread - pread 4 __libc_pread __libc_pread64 __pread pread __pread64 pread64
pwrite - pwrite 4 __libc_pwrite __libc_pwrite64 __pwrite pwrite __pwrite64 pwrite64
fstatfs - fstatfs i:ip __fstatfs fstatfs fstatfs64 __fstatfs64
Jakub
next prev parent reply other threads:[~2002-08-04 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 14:53 [PATCH] Fix Alpha build Jakub Jelinek
2002-08-04 15:28 ` Jakub Jelinek [this message]
2002-08-04 17:07 ` [PATCH] Fix IA-64 build Roland McGrath
2002-08-04 23:25 ` Jakub Jelinek
2002-08-04 23:59 ` Roland McGrath
2002-08-04 17:38 ` [PATCH] Fix Alpha build Ulrich Drepper
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=20020805002818.V20867@sunsite.ms.mff.cuni.cz \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).