public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Changes to flag-o-matic's _filter-var
Date: Sun, 7 Mar 2010 13:16:14 -0500	[thread overview]
Message-ID: <201003071316.14493.vapier@gentoo.org> (raw)
In-Reply-To: <4B93F78D.90300@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1592 bytes --]

On Sunday 07 March 2010 13:59:25 ChIIph wrote:
> On 03/07/10 14:50, Mike Frysinger wrote:
> > On Sunday 07 March 2010 12:54:34 ChIIph wrote:
> >> [snip]
> >> The commas are only added when there's LDFLAGS being changed.
> > 
> > you missed my point.  read the whole eclass -- this function isnt only
> > used on LDFLAGS.  your patch opens the door to incorrectly split/mangle
> > other variables.
> 
> I know, what I wanted to say is that I've tested those changes with more
> than filter-ldflags funtion, and I proposed it here because it works in
> every case.

no, it really doesnt.  it took me two seconds to put together an example where 
your change corrupted CFLAGS.  an unlikely value, but a valid value 
nonetheless, which means your proposal is unacceptable on that merit alone.

> >>> plus, there are a few other ways to trick the system.
> >>> 
> >>> my opinion is still:
> >>>  - bypassing the system is sometimes useful
> >>>  - use separate -Wl flags and things just work
> >> 
> >> Ok, but in the default profiles LDFLAGS are separated with commas, so
> >> for that second opinion to be possible, I think that should be changed.
> > 
> > i really have no idea what you're talking about.  no default profile uses
> > the multi-linker flag form.
> 
> grep -nR LDFLAGS /usr/portage/profiles/*
> (...)
> /usr/portage/profiles/default/linux/make.defaults:53:LDFLAGS="-Wl,-O1"
> (...)

how is that relevant ?  people use `filter-flags -Wl,-O1`, they dont use 
`filter-flags -O1`.  this is not multiple linker flags combined into one -Wl.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2010-03-07 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 20:27 [gentoo-dev] Changes to flag-o-matic's _filter-var ChIIph
2010-02-24 22:49 ` [gentoo-dev] " Duncan
2010-03-07  2:27 ` [gentoo-dev] " Mike Frysinger
2010-03-07 17:54   ` ChIIph
2010-03-07 17:50     ` Mike Frysinger
2010-03-07 18:59       ` ChIIph
2010-03-07 18:16         ` Mike Frysinger [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=201003071316.14493.vapier@gentoo.org \
    --to=vapier@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