From: Ned Ludd <solar@gentoo.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] per package cflags (was Re: Do we want optimal performance?)
Date: Wed, 08 Sep 2004 23:42:56 -0400 [thread overview]
Message-ID: <1094701375.9661.610.camel@simple> (raw)
In-Reply-To: <20040909022643.GE6455@curie-int.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1759 bytes --]
On Wed, 2004-09-08 at 22:26, Robin H. Johnson wrote:
> On Wed, Sep 08, 2004 at 09:51:15PM -0400, Travis Tilley wrote:
> > Daniel Goller wrote:
> > >although i am against overly tweaking CFLAGS, someone suggested
> > >something that might be more sane to ask for:
> > >
> > >/etc/portage/packages.cflags
> > >
> > >an easy way to maintain your cflags you worked so hard for to obtain,
> > >you can trade them in the forums or ebay and then append to your file,
> > >not much work to implement in my eyes, and all the testing work is done
> > >by those who want it
> > mkdir /etc/portage and copy this file there (MUCH thanks to solar for
> > writing this. he like... kicks ass an stuff). it implements an
> > /etc/portage/package.cflags without needing to patch portage. i think
> > this might require portage 2.0.51_pre... no idea, i havent used 2.0.50
> > in a while.
> [snip]
> Could this be generalized to do /etc/portage/package.env like somebody
> else asked for?
>
> And then simply put a CFLAGS line in the file referenced by package.env,
> as it seems that it really would belong there.
I played with that idea for a few mins, but unfortunately I found no
easy way in bash to deal with the quotes.
Assuming this syntax.
sys-apps/paxctl CFLAGS="-Os -fomit-frame-pointer"
sys-devel/gdb CFLAGS="-O2 -g3"
app-misc/beep FEATURES="sfperms sandbox" LDFLAGS="-Wl,-z,now
-Wl,-z,relro"
dev-libs/openssl CFLAGS="-O3 -fno-omit-frame-pointer -m32"
..
Maybe somebody else is motivated to do it from the basic idea. I gave up
and settled for the easy way out of package.cflags package.ldflags here
locally.
--
Ned Ludd <solar@gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-09 3:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 10:15 [gentoo-dev] Do we want optimal performance? Klavs Klavsen
2004-09-08 11:29 ` Paul de Vrieze
2004-09-08 12:03 ` Corvus Corax
2004-09-08 13:16 ` Paul de Vrieze
2004-09-08 12:19 ` Alin Nastac
2004-09-08 13:24 ` Marcus D. Hanwell
2004-09-08 13:43 ` Patrick Lauer
2004-09-08 14:21 ` Klavs Klavsen
2004-09-09 7:52 ` Paul de Vrieze
2004-09-08 12:49 ` Spider
2004-09-08 17:16 ` Robert Moss
2004-09-08 18:20 ` Chris Gianelloni
2004-09-08 19:11 ` Klavs Klavsen
2004-09-08 19:54 ` Paul de Vrieze
2004-09-08 20:05 ` Marcus D. Hanwell
2004-09-08 19:41 ` Lisa Seelye
2004-09-09 0:49 ` Daniel Goller
2004-09-09 1:51 ` [gentoo-dev] per package cflags (was Re: Do we want optimal performance?) Travis Tilley
2004-09-09 2:26 ` Robin H. Johnson
2004-09-09 3:42 ` Ned Ludd [this message]
2004-09-09 3:49 ` Robin H. Johnson
2004-09-09 17:23 ` Robert Moss
2004-09-09 4:41 ` Will Buckner
2004-09-09 4:51 ` Ciaran McCreesh
2004-09-09 6:07 ` [gentoo-dev] Do we want optimal performance? Klavs Klavsen
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=1094701375.9661.610.camel@simple \
--to=solar@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=robbat2@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