From: Steve Munroe <sjmunroe@us.ibm.com>
To: libc-hacker@sources.redhat.com, Thorsten Kukuk <kukuk@suse.de>
Subject: Re: [PATCH] PPC enable Alitvec hardware, part 3 revision b
Date: Fri, 16 Jan 2004 16:39:00 -0000 [thread overview]
Message-ID: <OFB93ACC74.FD5CDCB5-ON86256E1D.005B2583-86256E1D.005B3C70@us.ibm.com> (raw)
Yes this is a conundrum. These changes are changing the ABI so must be
versioned but 2.3.3 is already shipped in a distro.
[sjmunroe@spokane3 sjmunroe]$ uname -a
Linux spokane3 2.4.21-3.EL #1 SMP Fri Sep 19 13:58:23 EDT 2003 ppc64 ppc64
ppc64 GNU/Linux
[sjmunroe@spokane3 sjmunroe]$ readelf -a /lib/libc.so.6 | grep getcontext
1652: 00046e4c 8 FUNC GLOBAL DEFAULT 10 getcontext@GLIBC_2.1
2044: 00046ce4 360 FUNC GLOBAL DEFAULT 10 getcontext@@GLIBC_2.3.3
5130: 00046ce4 360 FUNC LOCAL DEFAULT 10 __getcontext
5742: 00046e4c 8 FUNC LOCAL DEFAULT 10 __getcontext_stub
7860: 00046e4c 8 FUNC GLOBAL DEFAULT 10 getcontext@GLIBC_2.1
8252: 00046ce4 360 FUNC GLOBAL DEFAULT 10 getcontext@@GLIBC_2.3.3
So these changes must be against 2.3.4
Steven J. Munroe
Power Linux Toolchain Architect
IBM Corporation, Linux Technology Center
Thorsten Kukuk <kukuk@suse.de>
Sent by: libc-hacker-owner@sources.redhat.com
01/16/2004 01:30 AM
To: libc-hacker@sources.redhat.com
cc:
Subject: Re: [PATCH] PPC enable Alitvec hardware, part 3 revision b
On Thu, Jan 15, Ulrich Drepper wrote:
> I've applied the patches. Responsibility for any breakage they might
> cause is still yours.
It does not compile on PPC nor PPC64:
version GLIBC_2.3.4 not defined for libc
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
next reply other threads:[~2004-01-16 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 16:39 Steve Munroe [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 2:36 Steve Munroe
2004-01-16 4:51 ` Ulrich Drepper
2004-01-16 7:30 ` Thorsten Kukuk
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=OFB93ACC74.FD5CDCB5-ON86256E1D.005B2583-86256E1D.005B3C70@us.ibm.com \
--to=sjmunroe@us.ibm.com \
--cc=kukuk@suse.de \
--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).