On Fri, Dec 15, 2017 at 2:12 PM, Alan Grimes <alonz...@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
