public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
	GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: make check failure on x86-64 with abilist
Date: Wed, 19 Mar 2003 11:13:00 -0000	[thread overview]
Message-ID: <200303191105.h2JB55N24341@magilla.sf.frob.com> (raw)
In-Reply-To: Andreas Jaeger's message of  Wednesday, 19 March 2003 12:02:10 +0100 <ho8yvbtya5.fsf@byrd.suse.de>

> Patch is appended.  Ok to commit?

We'll wait for Ulrich and Jakub to comment.  

> > That means you didn't lose anything.  make check will always update all
> > .out files, and then do check-abi (show you the diff).
> 
> Excellent!

Actually if you use -j but not -k, check-abi could fail first and make it bail.
But it's unlikely.

  reply	other threads:[~2003-03-19 11:05 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 [this message]
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
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=200303191105.h2JB55N24341@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=aj@suse.de \
    --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).