Bug 427612 – firefox-14.0.1 does not emerge: double-conversion/utils.h:67:2: error Target architecture was not detected as supported

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Michael Volland 2012-07-22 09:06:57 UTC]

Created attachment 318892 [details]
emerge --info '=www-client/firefox-14.0.1' && build.log &&  emerge -pqv '=www-client/firefox-14.0.1'

firefox-14.0.1 does not emerge

Buildlog snippet:

In file included from /var/tmp/portage/www-client/firefox-14.0.1/work/mozilla-release/mfbt/double-conversion/bignum-dtoa.h:31:0,
                 from /var/tmp/portage/www-client/firefox-14.0.1/work/mozilla-release/mfbt/double-conversion/bignum-dtoa.cc:30:
/var/tmp/portage/www-client/firefox-14.0.1/work/mozilla-release/mfbt/double-conversion/utils.h:67:2: error: #error Target architecture was not detected as supported by Double-Conversion.In file included from /var/tmp/portage/www-client/firefox-14.0.1/work/mozilla-release/mfbt/double-conversion/bignum.h:31:0,
                 from /var/tmp/portage/www-client/firefox-14.0.1/work/mozilla-release/mfbt/double-conversion/bignum.cc:28:
/var/tmp/portage/www-client/firefox-14.0.1/work/mozilla-release/mfbt/double-conversion/utils.h:67:2: error: #error Target architecture was not detected as supported by Double-Conversion.

System: Powermac G5 late 2005. Kernel Linux 2.6.39.4 ACCEPT_KEYWORDS="~ppc64"
Last working Firefox is Ver. 13.0

[Comment 1 Jory A. Pratt 2012-07-23 16:22:41 UTC]

Created attachment 319002 [details, diff]
Ensure we define all appropriate archs

Drop it into /etc/portage/patches/www-client/firefox and emerge again please.

[Comment 2 Michael Volland 2012-07-24 10:32:42 UTC]

Attachment 319002 [details, diff] patch worked. I was able to emerge firefox-14.0.1
with this patch.

Thanks.
Michael

[Comment 3 Massimo Burcheri 2012-08-10 08:13:10 UTC]

www-client/firefox-14.0.1 was successfully built on amd64.
But the failure also appears on ppc, -> Add arches: PPC

[Comment 4 dehua.yang 2012-08-17 08:39:43 UTC]

(In reply to comment #2)
> Attachment 319002 [details, diff] [details, diff] patch worked. I was able to emerge
> firefox-14.0.1
> with this patch.
> 
> Thanks.
> Michael

Does it work? I emerged successfully with the patch, but it does not work: I typed 'firefox' in a gnome terminal, and it terminated in a few seconds without launching anything.

[Comment 5 Michael Volland 2012-08-17 17:37:40 UTC]

(In reply to comment #4)
> (In reply to comment #2)

> Does it work? I emerged successfully with the patch, but it does not work: I
> typed 'firefox' in a gnome terminal, and it terminated in a few seconds
> without launching anything.

Just the first start didn't work - then it did run.
In the moment I cannot make any further tests, since I've got another problem.
(No fonts in X) ( It's still possible to start firefox from a terminal, but without any fonts visible.)

By the way I used xterm and lxde from ~ppc64

[Comment 6 Jory A. Pratt 2012-08-28 21:04:23 UTC]

*** Bug 432680 has been marked as a duplicate of this bug. ***

[Comment 7 Joe Jezak (RETIRED) 2012-08-31 02:53:28 UTC]

For what it's worth, I can reproduce the same behavior as both of you on my PowerPC machines. Cairo is still bugged, I haven't figured out why yet, but Firefox crashes immediately for me if I use cairo. If I turn it off, I get fonts with the opposite colors in the UI, which seems to be an endianness issue. I'm trying to track down what code is doing the font rendering now.

[Comment 8 Jory A. Pratt 2012-08-31 03:23:49 UTC]

(In reply to comment #7)
> For what it's worth, I can reproduce the same behavior as both of you on my
> PowerPC machines. Cairo is still bugged, I haven't figured out why yet, but
> Firefox crashes immediately for me if I use cairo. If I turn it off, I get
> fonts with the opposite colors in the UI, which seems to be an endianness
> issue. I'm trying to track down what code is doing the font rendering now.

What version of cairo are you using? If you have not updated to 1.12 yet plz do so and retest.

[Comment 9 Jory A. Pratt 2012-09-02 17:49:28 UTC]

Fixed in version 15. Thanks for reporting.

[Comment 10 Michael Weber (RETIRED) 2012-09-02 18:17:15 UTC]

(In reply to comment #9)
> Fixed in version 15. Thanks for reporting.

Can you backport this to version 14.0.1, please.
You requested stabilization which is blocked for ppc by this issue (bug 427224). thanks.

[Comment 11 Jory A. Pratt 2012-09-02 19:27:43 UTC]

(In reply to comment #10)
> (In reply to comment #9)
> > Fixed in version 15. Thanks for reporting.
> 
> Can you backport this to version 14.0.1, please.
> You requested stabilization which is blocked for ppc by this issue (bug
> 427224). thanks.

14.0.1 was never suppose to be stabilized, esr releases and seamonkey are only thing we stabilize now, so firefox-10.0.6 would have been the stable canidate.

[Comment 12 Michael Weber (RETIRED) 2012-09-03 06:30:58 UTC]

(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #9)
> > > Fixed in version 15. Thanks for reporting.
> > 
> > Can you backport this to version 14.0.1, please.
> > You requested stabilization which is blocked for ppc by this issue (bug
> > 427224). thanks.
> 
> 14.0.1 was never suppose to be stabilized, esr releases and seamonkey are
> only thing we stabilize now, so firefox-10.0.6 would have been the stable
> canidate.

Right, sorry. Let's try to remember this when 14.0.1/15 get stable. Thanks for the comment.