public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/14995] glibc fails to build if gold is the default linker, even if ld.bfd is available
Date: Sat, 12 Oct 2013 00:36:00 -0000	[thread overview]
Message-ID: <bug-14995-131-Zwjix67NwL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14995-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14995

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|carlos at redhat dot com           |unassigned at sourceware dot org

--- Comment #8 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Ondrej Bilka from comment #7)
> Carlos, it was 9 months so gcc side should be resolved and we could return
> to fixing failures.

I'm not currently working on this so I'm going to unassign myself. The status
remains the same, but now with -fuse-ld or -fuse-gold things should be much
easier to test and fix. The testsuite regressions still need to be understood
before this gets enabled.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-10-12  0:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 12:21 [Bug build/14995] New: " Bernhard.Rosenkranzer at linaro dot org
2013-01-04 20:33 ` [Bug build/14995] " carlos at systemhalted dot org
2013-01-04 20:34 ` carlos at systemhalted dot org
2013-01-04 20:39 ` law at redhat dot com
2013-01-09  4:19 ` carlos at systemhalted dot org
2013-01-09  4:20 ` carlos at systemhalted dot org
2013-01-09  4:23 ` carlos at systemhalted dot org
2013-01-10 19:11 ` carlos at systemhalted dot org
2013-10-11 17:08 ` neleai at seznam dot cz
2013-10-12  0:36 ` carlos at redhat dot com [this message]
2014-06-13 19:09 ` fweimer at redhat dot com
2015-03-09 23:08 ` hjl.tools at gmail dot com
2015-03-09 23:25 ` hjl.tools at gmail dot com
2015-03-10 12:44 ` cvs-commit at gcc dot gnu.org
2015-03-10 12:59 ` hjl.tools at gmail dot com
2015-03-10 13:22 ` cvs-commit at gcc dot gnu.org

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=bug-14995-131-Zwjix67NwL@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).