On Wed, May 15, 2013 at 11:42:33AM +0200, Mike Hommey wrote: > Hi, > > With the increasing number of reports of local builds for Linux and > Android hitting the 32-bits address space limits when linking, and with > the fact that gcc 4.7 on try does hit that limit on PGO builds, it has > become necessary to switch the 32-bits Linux and Android builds to > 64-bits environments and toolchains. > > This switch is going to happen some time today (May 15).
So, interestingly, while buildbot reconfig was triggered yesterday, somehow it didn't make the builds actually switch to 32-bits environment. After Justin Wood did a re-reconfig this morning (european time), things got straight up... but non-clobber builds got red because of the python virtualenv still containing a 32-bits binary when the system python library is now 64-bits. While I think I triggered all the necessary clobbers on all branches where it's needed, but I didn't inspect all of them to retrigger failed builds. In the event there are some project branches with the following error: error while loading shared libraries: libpython2.7.so.1.0: wrong ELF class: ELFCLASS64 Please retrigger these builds after checking the clobberer says the last clobber is newer than 2013-05-16 01:10:00 PDT. > Following this, we're going to switch all Linux builds to gcc 4.7, later > this week. Chances are this is not going to happen this week. Something in the last 569 changesets before 15ba59a74221 broke some webgl mochitest when built with gcc 4.7. Filed bug 872960. Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
