From: "Paul Stear" <gentoo@appjaws.plus.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] glibc-2.12.1-r1 failure
Date: Mon, 27 Sep 2010 17:13:35 +0100 [thread overview]
Message-ID: <op.vjo8oxjwvnz6gd@pc2.homenet> (raw)
In-Reply-To: <AANLkTi=OXXg=Mi2eXF2kN83jAyLhDAXOoMQ9Ko+C1Edj@mail.gmail.com>
On Mon, 27 Sep 2010 16:13:42 +0100, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Mon, Sep 27, 2010 at 7:33 AM, Paul Stear <gentoo@appjaws.plus.com>
> wrote:
>> Hi all,
>> I think I have a symbolic link problem. Any thought on how to solve this
>> error.
> ...
>> unexpected reloc type in static binarymake[1]: ***
>> [install-symbolic-link]
> ...
>> LDFLAGS="-Wl,--as-needed,-O1 -Wl,--enable-new-dtags -Wl,--sort-common
>> -s"
>
> See this forum post:
>
> http://forums.gentoo.org/viewtopic-p-6395405.html
>
> Seems your LDFLAGS may be the culprint. Specifically this part of
> ssuominen's post:
>
> quote:
> -Wl,-s (or plain -s) breaks Portage's strip handling,
> FEATURES="nostrip", FEATURES="-nostrip". Also, toolchain packages,
> exactly like glibc handles stripping in very selective way -> Some of
> the installed binaries/libraries *can* be stripped, and some *cannot*.
> Just forcing stripping for everything is... like I said, insane
>
Thanks for the reply
What would sensible LDFLAGS be for my amd64 system
thanks again
Paul
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next prev parent reply other threads:[~2010-09-27 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 12:33 [gentoo-amd64] glibc-2.12.1-r1 failure Paul Stear
2010-09-27 13:58 ` [gentoo-amd64] " Duncan
2010-09-27 14:56 ` Paul Stear
2010-09-27 15:13 ` [gentoo-amd64] " Paul Hartman
2010-09-27 16:13 ` Paul Stear [this message]
2010-09-27 19:45 ` Josh Sled
2010-09-27 17:45 ` Paul Stear
2010-09-27 16:10 ` Frank Peters
2010-09-27 17:57 ` [gentoo-amd64] " Nikos Chantziaras
2010-09-29 11:12 ` [gentoo-amd64] " Paul Stear
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=op.vjo8oxjwvnz6gd@pc2.homenet \
--to=gentoo@appjaws.plus.com \
--cc=gentoo-amd64@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