From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] what gives with -O[x] in cflags?
Date: Fri, 15 Dec 2017 20:11:20 -0600 [thread overview]
Message-ID: <CAAD4mYi=EP-PV94uHmA-CcoQkmBv0FAx626JFpnjPomuDgq0zg@mail.gmail.com> (raw)
In-Reply-To: <46c2e11c-c78d-40d6-bc7a-378e91607651@verizon.net>
On Fri, Dec 15, 2017 at 2:12 PM, Alan Grimes <ALONZOTG@verizon.net> wrote:
> I did not have -O3 in my cflags because
>
> A> most packages have an appropriate -O level set
> B> Some packages are sensitive to the optimization flag and will
> missbehave if set,
> C> letting the optimization level default to whatever should always be
> safe.
>
> -> therefore I did not have any optimization set...
>
> So therefore webkit-gtk decides to be a prissy little cunt and throws an
> error because it didn't have an optimization flag set, who the hell do
> those developers think they are? If you think you should have an
> optimization flag SET IT!!! Just provide an override, throwing an error
> just because the user was lazy in compiling it is not acceptable. =|
>
I noticed something similar in Firefox, which from skimming the build
log sets -O3 internally regardless of what the user has set. This is
troubling for two reasons:
1) Gentoo (apparently) has a policy of not allowing packages to mangle
CFLAGS and CXXFLAGS, even with user permission (a useflag of eix was
removed because it set -O3 when enabled).
2) Firefox is the only application I run that crashes, and I don't
know how to disable -O3 to potentially make it more stable.
Cheers,
R0b0t1
next prev parent reply other threads:[~2017-12-16 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 20:12 [gentoo-user] what gives with -O[x] in cflags? Alan Grimes
2017-12-16 2:11 ` R0b0t1 [this message]
2017-12-16 2:53 ` Michael Orlitzky
2017-12-16 18:37 ` Andrew Lowe
2017-12-17 0:28 ` Peter Humphrey
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='CAAD4mYi=EP-PV94uHmA-CcoQkmBv0FAx626JFpnjPomuDgq0zg@mail.gmail.com' \
--to=r030t1@gmail.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