From: Iain Buchanan <iaindb@netspace.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] per-ebuild compil options
Date: Wed, 03 Oct 2007 10:08:42 +0930 [thread overview]
Message-ID: <1191371922.8586.34.camel@orpheus> (raw)
In-Reply-To: <20071002095650.5b09a58d@zaphod.digimed.co.uk>
On Tue, 2007-10-02 at 09:56 +0100, Neil Bothwick wrote:
> On Tue, 02 Oct 2007 14:04:10 +0930, Iain Buchanan wrote:
[snip]
> > eg. I would always want to build glib and glibc with nostrip in the
> > FEATURES, and -ggdb in the compile options, but all other ebuilds would
> > be as normal.
>
> mkdir -p /etc/portage/env.d/sys-devel
> echo 'FEATURES="blah nostrip"' >/etc/portage/env.d/sys-devel/gcc
> echo 'CFLAGS="blah -ggdb"' >>etc/portage/env.d/sys-devel/gcc
> etc.
hey that looks cool... except that it didn't work! I should be doing
this to dev-libs/glib and sys-libs/glibc right?
$ cat /etc/portage/env.d/dev-libs/glib
FEATURES="${FEATURES} nostrip"
CFLAGS="${CFLAGS} -ggdb"
$ sudo emerge -va1 glib
...
$ file /usr/lib/libglib-2.0.so.0.1400.1
/usr/lib/libglib-2.0.so.0.1400.1: ELF 32-bit LSB shared object, Intel
80386, version 1 (SYSV), stripped
it now says stripped, whereas last time when I specified FEATURES on the
command line before emerge, it came out as not stripped...
I also tried this:
$ cat /etc/portage/env.d/dev-libs/glib
FEATURES="fixpackages userpriv usersandbox userfetch nostrip"
CFLAGS="-O2 -march=pentium4 -pipe -ggdb"
CXXFLAGS="-O2 -march=pentium4 -pipe -ggdb"
and they still end up stripped...
any ideas why? thanks!
--
Iain Buchanan <iaindb at netspace dot net dot au>
There's no such thing as a free lunch.
-- Milton Friendman
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-03 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 4:34 [gentoo-user] per-ebuild compil options Iain Buchanan
2007-10-02 8:56 ` Neil Bothwick
2007-10-03 0:38 ` Iain Buchanan [this message]
2007-10-03 18:09 ` Bo Ørsted Andresen
2007-10-03 21:33 ` Neil Bothwick
2007-10-03 23:15 ` Iain Buchanan
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=1191371922.8586.34.camel@orpheus \
--to=iaindb@netspace.net.au \
--cc=gentoo-user@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