From: microcai <microcai@fedoraproject.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.18 build problem
Date: Mon, 28 Apr 2014 23:55:22 +0800 [thread overview]
Message-ID: <CAMgqO2xRYYUYduwXyeT7DLcdUi2oUCoac=-K5M+6n1GYn0r82A@mail.gmail.com> (raw)
In-Reply-To: <20140321164456.374c6261@gentoo.org>
2014-03-21 23:44 GMT+08:00 Tom Wijsman <TomWij@gentoo.org>:
> On Fri, 7 Mar 2014 18:43:27 +0800
> microcai <microcai@fedoraproject.org> wrote:
>
>> 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?
>>
>
> Can you file a bug at https://bugs.gentoo.org such that the maintainers
> are aware of this? That is, only if it is still reproducible today.
fixed. it's because of a wired CFLAGS -Bsymblic-functions that I put
into make.conf once for testing but forget to remove afterwards.
>
> --
> With kind regards,
>
> Tom Wijsman (TomWij)
> Gentoo Developer
>
> E-mail address : TomWij@gentoo.org
> GPG Public Key : 6D34E57D
> GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
>
prev parent reply other threads:[~2014-04-28 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:43 [gentoo-user] glibc-2.18 build problem microcai
2014-03-21 15:44 ` Tom Wijsman
2014-04-28 15:55 ` microcai [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='CAMgqO2xRYYUYduwXyeT7DLcdUi2oUCoac=-K5M+6n1GYn0r82A@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