public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Adding --as-needed to LDFLAGS in profiles/default/linux/make.defaults
Date: Mon, 28 Jun 2010 09:16:32 +0100	[thread overview]
Message-ID: <20100628091632.14dca3c9@snowcone> (raw)
In-Reply-To: <4C285876.4020208@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]

On Mon, 28 Jun 2010 11:08:22 +0300
Samuli Suominen <ssuominen@gentoo.org> wrote:
> This is not about optimizing but preventing clear breakage, the
> benefits of asneeded are not under debate here (like already stated
> in the original message this thread started from)

--as-needed does not prevent breakage. It shoves some breakages under
the carpet so they're sometimes less visible, and sometimes easier to
fix when they happen. However, it does absolutely nothing to address
any of the root causes of the breakage, and it does introduce new
breakages itself.

Had one tenth of the effort that had been put into running around and
adding in hacks to work around a deliberately broken toolchain instead
been put into fixing libtool and delivering better slotting mechanisms,
none of this would be an issue.

Or is the policy "we've started running towards the cliff and we've
already debated the merits of jumping off it, so all you're allowed to
discuss now is how we remove the fence"?

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2010-06-28  8:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28  1:09 [gentoo-dev] Adding --as-needed to LDFLAGS in profiles/default/linux/make.defaults Nirbheek Chauhan
2010-06-28  7:23 ` [gentoo-dev] " Christian Faulhammer
2010-06-28  7:35 ` [gentoo-dev] " Ciaran McCreesh
2010-06-28  7:44   ` Samuli Suominen
2010-06-28  7:51     ` Ciaran McCreesh
2010-06-28  8:04       ` [gentoo-dev] " Nikos Chantziaras
2010-06-28  8:08       ` [gentoo-dev] " Samuli Suominen
2010-06-28  8:10         ` Nirbheek Chauhan
2010-06-28 13:43           ` Thomas Anderson
2010-06-28 13:59             ` Roy Bamford
2010-06-28 14:05               ` Ciaran McCreesh
2010-06-29  3:30                 ` Jeroen Roovers
2010-06-29  7:23                   ` Ciaran McCreesh
2010-06-29  8:46                     ` Alex Alexander
2010-06-29 17:25                       ` David Leverton
2010-06-29 17:59                         ` Alex Alexander
2010-07-05 13:01                 ` [gentoo-dev] " Peter Hjalmarsson
2010-07-05 13:47                   ` Arun Raghavan
2010-07-05 14:25                   ` David Leverton
2010-06-28  8:16         ` Ciaran McCreesh [this message]
2010-06-28 11:09           ` Duncan
2010-06-28 11:46             ` David Leverton
2010-06-28 15:21               ` Brian Harring
2010-06-29  6:27                 ` [gentoo-dev] [OT] h v l Mike Frysinger
2010-06-29  6:35                   ` Luis Araujo
2010-06-28  8:17 ` [gentoo-dev] Adding --as-needed to LDFLAGS in profiles/default/linux/make.defaults Markos Chandras
2010-06-28  9:21   ` Nirbheek Chauhan
2010-06-28  8:42 ` Pacho Ramos
2010-06-28 12:11 ` Alex Alexander
2010-06-29 17:04 ` David Leverton

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=20100628091632.14dca3c9@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --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