From: "Carlos O'Donell" <carlos@redhat.com>
To: Roland McGrath <roland@hack.frob.com>,
"GNU C. Library" <libc-alpha@sourceware.org>
Cc: binutils@sourceware.org
Subject: Re: gold vs libc
Date: Sun, 30 Mar 2014 18:28:00 -0000 [thread overview]
Message-ID: <53386231.6010107@redhat.com> (raw)
In-Reply-To: <20140330042516.1A88E74481@topped-with-meat.com>
On 03/30/2014 12:25 AM, Roland McGrath wrote:
> On the glibc.git branch roland/gold-vs-libc is the trivial configure change
> necessary to let glibc attempt to build using gold as the linker. (The
> version check with that change is excessively loose--to boot, it admits
> current gold versions so you can test, even though they don't work enough.)
Enabling gold is BZ #14995.
https://sourceware.org/bugzilla/show_bug.cgi?id=14995
... and to link to the old discussion with more patches for
configure:
https://sourceware.org/ml/libc-alpha/2013-01/msg00274.html
Cheres,
Carlos.
prev parent reply other threads:[~2014-03-30 18:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 4:25 Roland McGrath
2014-03-30 4:56 ` Alan Modra
2014-03-30 5:09 ` Roland McGrath
2014-03-31 19:03 ` Ian Lance Taylor
2014-03-31 20:04 ` Roland McGrath
2014-03-31 20:53 ` Ian Lance Taylor
2014-03-31 21:40 ` Roland McGrath
2014-04-01 18:25 ` Ian Lance Taylor
2014-09-10 20:56 ` Cary Coutant
2014-09-10 22:05 ` Rafael Espíndola
2014-09-11 0:32 ` Alan Modra
2014-09-10 22:52 ` Roland McGrath
2014-09-11 0:04 ` Ian Lance Taylor
2014-12-20 13:58 ` PATCH: PR gold/14675: No eh_frame info registered in exception_static_test H.J. Lu
2014-12-22 17:37 ` Cary Coutant
2014-12-22 22:40 ` H.J. Lu
2014-12-23 0:58 ` H.J. Lu
2015-01-07 13:17 ` H.J. Lu
2015-01-07 14:43 ` H.J. Lu
2015-01-07 18:50 ` Cary Coutant
2015-01-26 17:22 ` H.J. Lu
2015-03-02 16:03 ` H.J. Lu
2015-03-09 17:16 ` Cary Coutant
2015-03-09 17:22 ` H.J. Lu
2015-03-20 15:41 ` H.J. Lu
2014-09-11 16:00 ` gold vs libc Cary Coutant
2014-09-11 16:05 ` Cary Coutant
2014-09-11 16:45 ` Rafael Espíndola
2014-09-11 16:21 ` Ian Lance Taylor
2014-09-11 18:33 ` Roland McGrath
2014-03-30 18:28 ` Carlos O'Donell [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=53386231.6010107@redhat.com \
--to=carlos@redhat.com \
--cc=binutils@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=roland@hack.frob.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).