public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Steven Munroe <sjmunroe@us.ibm.com>
To: libc-hacker@sources.redhat.com
Subject: Re: vm86 system call update
Date: Wed, 03 Dec 2003 15:49:00 -0000	[thread overview]
Message-ID: <3FCE05F6.10608@us.ibm.com> (raw)

Ulrich Drepper writes:

 > Roland McGrath wrote:
 >
 > > No, there has been no GNU C Library 2.3.3 release yet.
 >
 > There has.  Face it.

So which is it? To add VMX support to powerpc64 I need to version 
setjmp/longjmp and [get | make | set | swap]context. More specifically I 
need to be backward compatible to what shipped in RHEL 3. On my resently 
  installed RHEL 3 GA system I see /lib64/libc-2.3.2.so. But when I run:

readelf -a /lib64/libc-2.3.2.so | grep 'GLIBC_2\.3\.'

I see a significant number of *@@GLIBC_2.3.3 symbols. For example:

     74: 0000000000127484    60 FUNC    GLOBAL DEFAULT   10 
.gnu_dev_makedev@@GLIBC_2.3.3
     94: 000000000014b7e4    64 FUNC    GLOBAL DEFAULT   10 
.inet6_option_init@@GLIBC_2.3.3

So is GLIBC_2.3.3 (effectively) released? And any ABI changes need to be 
  targeted for GLIBC_2.3.4?

             reply	other threads:[~2003-12-03 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 15:49 Steven Munroe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-02 23:49 Roland McGrath
2003-12-03  0:05 ` Ulrich Drepper
2003-12-03  0:09   ` Jakub Jelinek
2003-12-03  0:27     ` Ulrich Drepper
2003-12-03  0:12   ` Roland McGrath
2003-12-03  0:24     ` Ulrich Drepper
2003-12-03  0:13   ` Roland McGrath

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=3FCE05F6.10608@us.ibm.com \
    --to=sjmunroe@us.ibm.com \
    --cc=libc-hacker@sources.redhat.com \
    --cc=sjmunroe@vnet.ibm.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).