From: Andreas Jaeger <aj@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Andreas Schwab <schwab@suse.de>,
Roland McGrath <roland@redhat.com>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: make check failure on x86-64 with abilist
Date: Sat, 22 Mar 2003 23:41:00 -0000 [thread overview]
Message-ID: <u865qbdh5m.fsf@gromit.moeb> (raw)
In-Reply-To: <20030319183136.I1717@sunsite.ms.mff.cuni.cz> (Jakub Jelinek's message of "Wed, 19 Mar 2003 18:31:36 +0100")
Jakub Jelinek <jakub@redhat.com> writes:
> On Wed, Mar 19, 2003 at 09:25:19AM -0800, Ulrich Drepper wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Andreas Jaeger wrote:
>> > Ok, is the obvious change then ok to commit?
>>
>> Not so fast, we'll have to check some old code first.
>
> E.g. /usr/bin/gettext from RHL5.2 has:
> 0804ce78 01b05 R_386_COPY 0804ce78 _nl_domain_bindings
> while in 6.2 it already does not.
> I have seen _nl_msg_cat_cntr and _nl_default_dirname in all
> gettext versions I looked at as != SHN_UND symbols though.
So, we cannot get rid of it - but how do we fix the abi-check failure?
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2003-03-22 6:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 9:36 Andreas Jaeger
2003-03-19 9:44 ` Jakub Jelinek
2003-03-19 10:31 ` Andreas Jaeger
2003-03-19 10:50 ` Roland McGrath
2003-03-19 10:53 ` Andreas Jaeger
2003-03-19 11:02 ` Roland McGrath
2003-03-19 11:05 ` Andreas Jaeger
2003-03-19 11:13 ` Roland McGrath
2003-03-19 12:22 ` Andreas Schwab
2003-03-19 12:55 ` Andreas Jaeger
2003-03-19 14:29 ` Andreas Schwab
2003-03-19 17:24 ` Andreas Jaeger
2003-03-19 17:31 ` Ulrich Drepper
2003-03-19 22:06 ` Jakub Jelinek
2003-03-22 23:41 ` Andreas Jaeger [this message]
2003-03-19 17:24 ` Ulrich Drepper
2003-03-19 17:25 ` 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=u865qbdh5m.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@redhat.com \
--cc=schwab@suse.de \
/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).