public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix glibc binary compatibility problems
Date: Fri, 21 Jun 2002 22:14:00 -0000	[thread overview]
Message-ID: <1024722836.2240.78.camel@myware.mynet> (raw)
In-Reply-To: <20020607120559.M20867@sunsite.ms.mff.cuni.cz>

[-- Attachment #1: Type: text/plain, Size: 953 bytes --]

On Fri, 2002-06-07 at 03:05, Jakub Jelinek wrote:

> readelf -a /lib/i686/libc.so.6 | grep gethostent_r | less
>   1062: 420f87e0   198 FUNC    GLOBAL DEFAULT   11 gethostent_r@GLIBC_2.0
>   1380: 420f87e0   198 FUNC    LOCAL  DEFAULT   11 __old_gethostent_r
>   1494: 420f8720   187 FUNC    LOCAL  HIDDEN   11 gethostent_r@@GLIBC_2.1.2
>   2108: 420f8720   187 FUNC    LOCAL  HIDDEN   11 __gethostent_r
>   3441: 420f87e0   198 FUNC    GLOBAL DEFAULT   11 gethostent_r@GLIBC_2.0
> and similarly for all other get*ent_r functions, plus _IO_wfile_jumps
> is not exported either but used to be (@@GLIBC_2.2).

I've applied parts of the patch.  I do not know why _IO_wfile_jumps is
needed.  What package is using it?

-- 
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-06-22  5:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07  3:06 Jakub Jelinek
2002-06-21 22:14 ` Ulrich Drepper [this message]

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=1024722836.2240.78.camel@myware.mynet \
    --to=drepper@redhat.com \
    --cc=jakub@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).