firefox-32.0

[Fernando de Oliveira]

​ftp://ftp.mozilla.org/pub/firefox/releases/32.0/source/firefox-32.0.source.tar.bz

[rt]

Fails in the install step for me (on i686):

resource://gre/components/Payment.js
resource://gre/components/PaymentFlowInfo.js
resource://gre/components/PeerConnection.js
resource://gre/components/PermissionPromptService.js
Traceback (most recent call last):
  File "/src/tmp/mozilla-release/toolkit/mozapps/installer/packager.py", line 402, in <module>
    main()
  File "/src/tmp/mozilla-release/toolkit/mozapps/installer/packager.py", line 394, in main
    args.source, gre_path, base)
  File "/src/tmp/mozilla-release/toolkit/mozapps/installer/packager.py", line 158, in precompile_cache
    errors.fatal('Error while running startup cache precompilation')
  File "/src/tmp/mozilla-release/python/mozbuild/mozpack/errors.py", line 101, in fatal
    self._handle(self.FATAL, msg)
  File "/src/tmp/mozilla-release/python/mozbuild/mozpack/errors.py", line 96, in _handle
    raise ErrorMessage(msg)
mozpack.errors.ErrorMessage: Error: Error while running startup cache precompilation
/src/tmp/mozilla-release/toolkit/mozapps/installer/packager.mk:714: recipe for target 'stage-package' failed
make[2]: *** [stage-package] Error 1
make[2]: Leaving directory '/src/tmp/mozilla-release/firefox-build-dir/browser/installer'
/src/tmp/mozilla-release/browser/build.mk:21: recipe for target 'install' failed
make[1]: *** [install] Error 2
make[1]: Leaving directory '/src/tmp/mozilla-release/firefox-build-dir'
client.mk:407: recipe for target 'install' failed
make: *** [install] Error 2

[ken@…]

Works for me on x86_64 (recent LFS-svn) - I've just done an unlogged DESTDIR install. A lot of noise in gre/modules/ (gre/components has rolled out of my term's buffer).

[ken@…]

I can confirm the problem on my sole i686 system.

​http://forums.mozillazine.org/viewtopic.php?f=42&t=2855045

The easier solution there appears to be to add (for i686)

--disable-optimize

I'll give that a try, but this machine is _slow_

[ken@…]

Some things I noticed in the configure file:

--with-mozilla-api-keyfile=file   Use the secret key contained in the given keyfile for Mozilla API requests
--with-google-api-keyfile=file   Use the secret key contained in the given keyfile for Google API requests
--with-bing-api-keyfile=file   Use the client id and secret key contained in the given keyfile for Bing API requests

I assume we do not want those.

Also, there is an option

ac_add_options --enable-default-toolkit=cairo-gtk3

I'm trying that at the moment, my impression is that I will not be using it again until a later release: with (apparently) no gtk3 theme set, firefox's menus are black and text mostly only appears when the mouse is over that line. In particular, this makes my Bookmarks menu very hard to navigate, and searches in google have a similar problem (black menu when right clicking, e.g. to open in new tab or new window). Also, the trac icons below 'Add a comment' have gone, only a row of plain white boxes - fortunately the help text is still there when I mouse over them. And I think that background colours on the Preview and Submit changes, and on the list of tickets, have gone - they all seem to be on a white background.

I _hope_ that is specific to gtk+-3, will have to do another build to find out.

[ken@…]

Replying to ken@…:

I can confirm the problem on my sole i686 system.

​http://forums.mozillazine.org/viewtopic.php?f=42&t=2855045

The easier solution there appears to be to add (for i686)

--disable-optimize

I'll give that a try, but this machine is _slow_

That successfully completes a DESTDIR install. If we do this, I guess we can add a sed _after_ creating the mozconfig, with a note that in this version of firefox the install breaks on 32-bit systems if the build is optimized. I'm using this:

test $(uname -m) = "i686" && sed -i 's/enable-optimize/disable-optimize' mozconfig || true

I guess that the book would also need the

|| true

so that it can be followed by &&.

[ken@…]

<sigh/> With the default (gtk2) build, the menus are ok. But visual "things" are missing everywhere. Here (the blfs wiki), background colours, and the icons for track edits. In fact colours seem to be missing at many sites, e.g. the front page of slashdot has lost its green "banner" and the newer/older tabs come up as blue text on white. At google, no picture or logo.

I'm not convinced that I want to upgrade my machines :-(

[Fernando de Oliveira]

ĸen, this sounds really bad. I will download Mozilla's binary just to test it. Please, with all respect, would you mind also doing that, just to check if something new might been missed?

[ken@…]

Replying to fo:

ĸen, this sounds really bad. I will download Mozilla's binary just to test it. Please, with all respect, would you mind also doing that, just to check if something new might been missed?

I was asleep. Meanwhile, I had asked a question on lwn.net, and at least one person has it working ok with the cairo-gtk2 toolkit. So, I powered up and discovered that a system with ff-31 also lost its colours - I share ~/ across all my systems. Digging down, the profile directory in ~/.mozilla/firefox had been updated each time I started firefox. Restoring that directory from a backup before my first update has fixed this on both 31 and the cairo-gtk2 build.

So, I now assume that cairo-gtk3 caused the problem. Will do another cairo-gtk2 build on a system which is still using 31, to check that.

[ken@…]

Replying to ken@…:

So, I now assume that cairo-gtk3 caused the problem. Will do another cairo-gtk2 build on a system which is still using 31, to check that.

Yeah, seems ok, background colours and icons for bold/italic/etc all present. Sorry for the noise.

[Fernando de Oliveira]

No worries. Thanks for checking.

[ken@…]

r14206

[ken@…]

For i686, I forgot the sed to fix it. That was in r14207.

[Armin K]

Now there seems to be another issue on x86_64 with 32.0.3, where --enable-optimize would cause linking to fail for me. I suppose it could be removed entirely as it brings nothing but trouble lately.