Simon Strandman posted <436F70C0.1040303@...>, excerpted below, on
Mon, 07 Nov 2005 16:20:32 +0100:
> The mozconfig eclass strips flags down to -O1 on amd64 with the
> explanation "more than -O1 causes segfaults on 64-bit (bug 33767)". That
> bug is two years old and we have a much improved amd64 toolchain since.
> I've been compiling firefox and and mozilla with -O2 and -Os for quite
> some time and never had any problems at all. And this is also what
> binary distros does. I opened a bug about it but nobody responded:
> So please test compiling firefox and other mozilla apps with -O2 and
> respond to that bug so this can be fixed!
For something of this nature (definitely 64-bit/amd64 related, and where
the amd64 arch testers (ATs) can be put to work confirming the results,
especially since the package owners may not be able to test...), it
generally works much better to either assign it to amd64@, or assign it to
the package owner (as you did) but CC amd64@ (as you did /not/).
Apparently, many of the herds, and I'd guess mozilla is one of them, are
really stretched far too thin, and for something like this that's going to
require a lot of testing they don't have the direct ability to do, and
where it's working as is, what resources there are will likely get
prioritized to security bugs and the like, since they can't do much with
this directly anyway. Get amd64@ in the CC (or assign it to them
originally if appropriate, as I think it could have been here), and it's
likely to get action rather sooner than it might otherwise.
(Me... I find konqueror, which I have on my system anyway since KDE's my
default desktop, to be quite sufficient. Merging Firefox/Mozilla would
just mean one more package to continually compile from source to keep
updated -- and a security critical package at that.)
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
email@example.com mailing list