public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <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: Tue, 10 Mar 2015 12:44:00 -0000 [thread overview]
Message-ID: <bug-14995-131-HaKGk6Sr2Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14995-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14995
--- Comment #11 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".
The branch, hjl/pr14995 has been created
at 0eb345cb8844391881de0a53c6ad36917bbf4453 (commit)
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0eb345cb8844391881de0a53c6ad36917bbf4453
commit 0eb345cb8844391881de0a53c6ad36917bbf4453
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Mon Mar 9 09:16:26 2015 -0700
Support build glibc with gold as default linker
The gold linker has no builtin default linker script and it can't be
to create shared libraries. Unless --enable-gold is used, it should
only be used to create executables. Use -fuse-ld=bfd to create shared
libraries.
[BZ #14995]
* Makerules (shlib-LDFLAGS): New.
($(common-objpfx)shlib.lds): Use it.
(build-shlib): Likewise.
(build-module-helper): Likewise.
($(common-objpfx)libc_pic.os): Likewise.
* config.make.in (use-bfd): New.
* configure: Regenerated.
* configure.ac: Add --enable-gold.
Accept gold 1.11 or higher.
(libc_cv_cc_use_bfd): Set to yes if -fuse-ld=bfd works. AC_SUBST.
(LDBFDFLAGS): New.
Use $LDBFDFLAGS to check if default -shared layout is sufficient.
-----------------------------------------------------------------------
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-03-10 12:44 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
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 [this message]
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-HaKGk6Sr2Z@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).