public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: LD_AS_NEEDED="1" in profiles/targets/developer/make.defaults?
Date: Sat, 03 Oct 2009 23:27:41 +0300	[thread overview]
Message-ID: <4AC7B3BD.3030903@gentoo.org> (raw)
In-Reply-To: <20091003201521.GM19056@gentoo.org>

Fabian Groffen wrote:
> On 03-10-2009 22:35:58 +0300, Samuli Suominen wrote:
>> Ciaran McCreesh wrote:
>>> On Sat, 03 Oct 2009 22:13:59 +0300
>>> Samuli Suominen <ssuominen@gentoo.org> wrote:
>>>> Since new binutils will support LD_AS_NEEDED="1" to force ld behave
>>>> asneeded we could use this for the developer -target in profiles?
>>>>
>>>> Speak up if you think it's a terrible idea.
>>> Well, it does break correct code, so it's about on par with forcing
>>> -ffast-math or -fno-exceptions or -fvisibility-inlines-hidden on
>>> globally...
>>>
>> Be reasonable. We can add -Wl,--no-as-needed for those packages with
>> valid code. And I'm certainly not suggesting adding it to base/, _only_
>> for the developer target.
> 
> Please recall that this is a GNU binutils flag.  I prefer the
> environment flag over the command-line option, because it doesn't break
> other linkers, but if it implies many ebuilds getting -Wl,--no-as-needed
> append-ldflagged, then I'm not getting happy as that breaks my builds.
> 
> 

The amount of pkgs in tree with valid code that fails with asneeded is
close to zero. We can use this,

if use userland_GNU; then
append-ldflags -Wl,--no-as-needed
fi

logic so it won't cause you troubles. Or the obvious shorter && version
of it.



  reply	other threads:[~2009-10-03 20:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03 19:13 [gentoo-dev] RFC: LD_AS_NEEDED="1" in profiles/targets/developer/make.defaults? Samuli Suominen
2009-10-03 19:18 ` Tomáš Chvátal
2009-10-03 19:25 ` Arfrever Frehtes Taifersar Arahesis
2009-10-03 19:28   ` Samuli Suominen
2009-10-03 19:29 ` Ciaran McCreesh
2009-10-03 19:35   ` Samuli Suominen
2009-10-03 20:15     ` Fabian Groffen
2009-10-03 20:27       ` Samuli Suominen [this message]
2009-10-03 20:33         ` Fabian Groffen
2009-10-03 20:40           ` Samuli Suominen
2009-10-03 21:11             ` Samuli Suominen
2009-10-03 21:13               ` Fabian Groffen
2009-10-04 10:13                 ` Samuli Suominen
2009-10-04 10:30                   ` Fabian Groffen
2009-10-03 20:21 ` [gentoo-dev] " Ryan Hill
2009-10-03 21:35   ` Samuli Suominen
2009-10-05  2:03   ` Peter Hjalmarsson
2009-10-05  6:10     ` Ryan Hill

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=4AC7B3BD.3030903@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@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