From: Jakub Jelinek <jakub@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: [PATCH] Fix ia64 build
Date: Sun, 18 Apr 2004 02:02:00 -0000 [thread overview]
Message-ID: <20040417080155.GH514@sunsite.ms.mff.cuni.cz> (raw)
Hi!
2004-04-17 Jakub Jelinek <jakub@redhat.com>
* sysdeps/ia64/memcmp.S (memcmp): Remove BP_SYM from
libc_hidden_builtin_def.
--- libc/sysdeps/ia64/memcmp.S.jj 2004-04-13 10:42:54.000000000 +0200
+++ libc/sysdeps/ia64/memcmp.S 2004-04-17 11:26:26.801401510 +0200
@@ -162,4 +162,4 @@ ENTRY(memcmp)
END(memcmp)
weak_alias (memcmp, bcmp)
-libc_hidden_builtin_def (BP_SYM (memcmp))
+libc_hidden_builtin_def (memcmp)
Jakub
next reply other threads:[~2004-04-18 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 2:02 Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-03 22:52 Jakub Jelinek
2002-05-10 13:59 Jakub Jelinek
2002-05-10 22:12 ` Andreas Jaeger
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=20040417080155.GH514@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).