On 05/09/2015 01:25 AM, Steve Langasek wrote: >> firefox: https://launchpad.net/bugs/1451453 >> arm64 only, not a regression > > firefox failed to build on both arm64 and ppc64el in the toolchain test > rebuild, but only failed on arm64 in a no-change rebuild.
to make it clear, there never was a "no-change rebuild". no, ppc64el isn't a regression, it successfully built in the updates test rebuild. > /usr/bin/ld.bfd.real: ../libjs_static.a(linux64.o): ABI version 1 is not > compatible with ABI version 2 output > /usr/bin/ld.bfd.real: failed to merge target specific data of file > ../libjs_static.a(linux64.o) > /usr/bin/ld.bfd.real: ../libjs_static.a(linux64_closure.o): ABI version 1 is > not compatible with ABI version 2 output > /usr/bin/ld.bfd.real: failed to merge target specific data of file > ../libjs_static.a(linux64_closure.o) > > https://launchpad.net/ubuntu/+archive/test- > rebuild-20150317/+build/7074123 > > This looks to me like a toolchain-related regression. this points to a toolchain issue, however it is not a regression. the arm64 firefox failed to build before with an internal compiler error, which I fixed, and now fails later with a linker error. >> flite: https://launchpad.net/bugs/1451462 >> fails to unpack (fuzz in diff) > > Do we know why this problem affected the toolchain test rebuild, but not > the no-change test rebuild? The behavior of dpkg-source in the trusty > build environment should not have changed since March. again, there was no "no change rebuild". >> gcc-4.8: >> part of the proposed updates > > There is also a build failure of gcc-4.7 on ppc64el, is that part of the > update? no, there never was a ppc64el port for gcc-4.7. > Please address the firefox/ppc64el and gcc-4.7 questions. from my point of view, these are non-issues. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1311866 Title: update binutils and GCC for trusty Status in binutils package in Ubuntu: Invalid Status in gcc-4.8 package in Ubuntu: Invalid Status in binutils source package in Trusty: Confirmed Status in gcc-4.8 source package in Trusty: Confirmed Status in binutils source package in Utopic: Invalid Status in gcc-4.8 source package in Utopic: Invalid Bug description: an SRU issue to document the update of gcc-4.8 in trusty 14.04 LTS saw two new architectures, arm64 and ppc64el. These require some updates for the toolchain. binutils takes some selected patches to fix specific issues, and gcc-4.8 takes the state of the current gcc-4.8 fsf branch to update the compiler. Changes and addresses issues are mentioned in the debian changelog. Packages are prepared in the ubuntu-toolchain-r/ppa PPA, and a test rebuild of the archive was done on all architectures using this PPA. The results of this test rebuild look ok (for all of the -release, -updates and -security pockets). As a further test, the linux (see bug #1383474), firefox and libreoffice packages were rebuilt, tested and found working. The test rebuild archives are: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140911-trusty.html http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140912-trusty.html http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140913-trusty.html gcc-4.8 should be built with the new binutils. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1311866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
