public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU libc <libc-alpha@sources.redhat.com>,
	glibc-bugs@sourceware.org, 	Ulrich Drepper <drepper@redhat.com>
Subject: Re: commit 9da4bb316ffa558b1001e5441d2ba919ebb2cf13 broke strcmp.S compile
Date: Fri, 27 Aug 2010 14:58:00 -0000	[thread overview]
Message-ID: <AANLkTi==1hyc5WUW4xfy+hpd1mLGZXzyUKreRduYByZv@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin27DFjSyvCHdAzywmHNvuu9voqoXOwnEV1MfKG@mail.gmail.com>

On Fri, Aug 27, 2010 at 10:24 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Thu, Aug 26, 2010 at 9:21 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:

> FWIW, glibc builds fine for me on Fedora 13/x86-64.

Are you definitely sure you're building everything from "fresh". I've
been git pulling and applied all these patches and my glibc was still
compiling fine, but the problem only shows up when I did a fresh
compile and that's when the problem occurred.

Thanks,
Jeff


  reply	other threads:[~2010-08-27 14:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27  4:21 Jeff Chua
2010-08-27 14:25 ` H.J. Lu
2010-08-27 14:58   ` Jeff Chua [this message]
2010-08-27 18:36     ` H.J. Lu
2010-08-27 19:10 ` Mike Frysinger
2010-08-28  0:35   ` Jeff Chua
2010-08-30 13:47     ` Jeff Chua

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='AANLkTi==1hyc5WUW4xfy+hpd1mLGZXzyUKreRduYByZv@mail.gmail.com' \
    --to=jeff.chua.linux@gmail.com \
    --cc=drepper@redhat.com \
    --cc=glibc-bugs@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@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).