From: microcai <microcai@fedoraproject.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] glibc-2.18 build problem
Date: Fri, 7 Mar 2014 18:43:27 +0800 [thread overview]
Message-ID: <CAMgqO2z03dxSHT9fEK9fe4Gy8ZrEXhC8YH9AjTHSTUB43UJtjw@mail.gmail.com> (raw)
I'm having trouble compiling glibc. No matter I tried with binutils
2.23 2.24. or -9999 live version, I got ld internal error in
x86_64_relocation . And the same error repeated with glibc-2.18 and
glibc-2.19 .
Don't know why . The google bring me a old bug report about
x86_64_relocation internal error when used conjunction with
IFUNC, but that doesn't seems to be related with mine problem.
When I first try to update glibc to 2.18, it's fine. but then the
attempt to update glibc to 2.18-r1 failed with ld internal
error. This error remains with glibc-2.16-r2 and glibc-2.19,
regardless of binutils version.
Does anyone have had the same problem?
next reply other threads:[~2014-03-07 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:43 microcai [this message]
2014-03-21 15:44 ` [gentoo-user] glibc-2.18 build problem Tom Wijsman
2014-04-28 15:55 ` microcai
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=CAMgqO2z03dxSHT9fEK9fe4Gy8ZrEXhC8YH9AjTHSTUB43UJtjw@mail.gmail.com \
--to=microcai@fedoraproject.org \
--cc=gentoo-user@lists.gentoo.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