public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Bernhard.Rosenkranzer at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/14995] New: glibc fails to build if gold is the default linker, even if ld.bfd is available
Date: Fri, 04 Jan 2013 12:21:00 -0000 [thread overview]
Message-ID: <bug-14995-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14995
Bug #: 14995
Summary: glibc fails to build if gold is the default linker,
even if ld.bfd is available
Product: glibc
Version: 2.17
Status: NEW
Severity: normal
Priority: P2
Component: build
AssignedTo: unassigned@sourceware.org
ReportedBy: Bernhard.Rosenkranzer@linaro.org
CC: carlos@systemhalted.org
Classification: Unclassified
If gold is the default linker, but ld.bfd is available (binutils compiled with
--enable-ld --enable-gold=default), glibc configure fails:
checking version of
/usr/lib/gcc/armv7hl-mandriva-linux-gnueabi/4.7.3/../../../../armv7hl-mandriva-linux-gnueabi/bin/ld...
v. ?.??, bad
[...]
configure: error:
*** These critical programs are missing or too old: ld
*** Check the INSTALL file for required versions.
If the configure script doesn't find a version of "ld" it can use, it should
check for "ld.bfd" in the same location.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-01-04 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 12:21 Bernhard.Rosenkranzer at linaro dot org [this message]
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
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@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).