From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How reliable is emerge --info output?
Date: Mon, 14 Jan 2013 05:45:19 -0600 [thread overview]
Message-ID: <20130114114519.GN11506@server> (raw)
In-Reply-To: <CAC=wYCFNz=MwXpCanqV4wY-YsA+NpfoLs+jLquFt8u1XjaLO-w@mail.gmail.com>
On Mon, Jan 14, 2013 at 10:18:32PM +1100, Adam Carter wrote:
> The first CFLAGS (or CXXFLAGS) line below appears to be taken from the
> environment setting, and the second is from the "<packagename> was built
> with the following" section of the emerge --info output.
>
> Squid looks as it should (the -flto is added to that package only) but for
> firefox it appears that -O2 has been stripped, and not replaced with -O3,
> which IIRC is the default for that package.
>
> # grep ^CFL /etc/make.conf
> CFLAGS="-march=amdfam10 -mcx16 -msahf -mpopcnt -mabm -O2 -pipe"
>
> # emerge --info squid | grep ^CFL
> CFLAGS="-march=amdfam10 -mcx16 -msahf -mpopcnt -mabm -O2 -pipe"
> CFLAGS="-march=amdfam10 -mcx16 -msahf -mpopcnt -mabm -O2 -pipe -flto"
>
> # emerge --info firefox | grep ^CFL
> CFLAGS="-march=amdfam10 -mcx16 -msahf -mpopcnt -mabm -O2 -pipe"
> CFLAGS="-march=amdfam10 -pipe -mno-avx"
>
> Is anyone getting O2 or O3 in their emerge --info firefox output?
mingdao@workstation ~ $ grep ^CFL /etc/portage/make.conf
CFLAGS="-march=native -O2 -pipe"
mingdao@workstation ~ $ emerge --info firefox | grep ^CFL
CFLAGS="-march=native -O2 -pipe"
CFLAGS="-march=native -pipe -mno-avx"
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-01-14 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 11:18 [gentoo-user] How reliable is emerge --info output? Adam Carter
2013-01-14 11:45 ` Bruce Hill [this message]
2013-01-14 12:05 ` Mark David Dumlao
2013-01-14 21:53 ` Adam Carter
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=20130114114519.GN11506@server \
--to=daddy@happypenguincomputers.com \
--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