From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: ChIIph <chiiph@gmail.com>
Subject: Re: [gentoo-dev] Changes to flag-o-matic's _filter-var
Date: Sun, 7 Mar 2010 12:50:03 -0500 [thread overview]
Message-ID: <201003071250.04043.vapier@gentoo.org> (raw)
In-Reply-To: <4B93E85A.6030908@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1789 bytes --]
On Sunday 07 March 2010 12:54:34 ChIIph wrote:
> On 03/06/10 23:27, Mike Frysinger wrote:
> > On Wednesday 24 February 2010 15:27:21 ChIIph wrote:
> >> Here are some minor changes I'd like to propose to flag-o-matic's
> >> _filter-var() to work properly with LDFLAGS.
> >> Without this, things like "-Wl,-O1,--as-needed" won't be affected by any
> >> kind of filter since there are no spaces to separate each flag.
> >>
> >> I don't know of any better way to do this, but here's a patch that works
> >> just fine.
> >
> > the func is used by other code where you dont want to screw with commas.
>
> 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.
> > 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.
> On the other hand, a lot of us use comma separated flags, so for all of
> us filter-ldflags doesn't work, and what I've modify doesn't mess with
> any of all the other function (or at least I haven't found the case in
> which it does).
then change your LDFLAGS
> Anyway, filter-ldflags doesn't work like it is right now, I'm not saying
> use _my_ code, but use whatever you think it's best to fix this.
i dont see any bug so you're going to have to be more specific
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-03-07 17:50 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 [this message]
2010-03-07 18:59 ` ChIIph
2010-03-07 18:16 ` Mike Frysinger
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=201003071250.04043.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=chiiph@gmail.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