public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Jaeger <aj@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: glibc ABI symbol list checking
Date: Fri, 27 Dec 2002 08:18:00 -0000	[thread overview]
Message-ID: <u8u1gzl9lh.fsf@gromit.moeb> (raw)
In-Reply-To: <200212262214.gBQMEKs06802@magilla.sf.frob.com> (Roland McGrath's message of "Thu, 26 Dec 2002 14:14:20 -0800")

Roland McGrath <roland@redhat.com> writes:

> Sorry if I wasn't clear about this.  They won't work until some reference
> files are installed, subdir/libfoo.abilist for each libfoo.so we build.  
> So start by touch locale/libBrokenLocale.abilist et al, and then check-abi
> should show you diffs containing the whole .symlist with +s, and update-abi
> will work.  

Ok, it works now for me.

>
> I had intended to get some initial reference lists in shortly after my
> first posting, but I've been sick this week.
>
>> For which platforms will you do the lists yourself - and for which do
>> you need help?
>
> Not sure yet.

I'm currently generating files for i.86-.*-linux.*.  Do you like to
have these?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

  reply	other threads:[~2002-12-27 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-23  3:40 Roland McGrath
2002-12-26  9:32 ` Andreas Jaeger
2002-12-26 14:14   ` Roland McGrath
2002-12-27  8:18     ` Andreas Jaeger [this message]
2002-12-27 12:30       ` Roland McGrath
2002-12-27 12:34     ` Andreas Jaeger
2002-12-27 12:53       ` Roland McGrath
2002-12-28  5:54         ` Andreas Jaeger
2002-12-28  6:01           ` Jakub Jelinek
2003-01-13  4:59       ` Andreas Jaeger
2003-01-15  8:51         ` 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=u8u1gzl9lh.fsf@gromit.moeb \
    --to=aj@suse.de \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@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).