touch-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

> 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.

/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.

> 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.

(In any case this is not an SRU blocker, because the problem is clearly
not toolchain-triggered.)

> 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?

> pygresql: https://launchpad.net/bugs/1451530
>         fails to build, needs fix from utopic

Reproducible here; but why did this build failure not show up in
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-
rebuild-20150317-updates-trusty.html ?

> thunderbird:
>         fails to build on arm64 and ppc64el, no regression.

And fixed in -updates.

> afaics, there is only one toolchain related build failure, u-boot.
> Both upstream and debian already stopped building that one,
> and this ZUMA platform was never supported in Ubuntu 14.04 LTS.

Indeed, u-boot is in main only because it's pulled in by jasper on
armhf; we don't appear to use u-boot at all on powerpc.  So this
behavior change (which may be a deliberate change rather than a bug), if
it only affects a single u-boot target on powerpc, doesn't seem to me
like a blocker for the toolchain update.

Please address the firefox/ppc64el and gcc-4.7 questions.

-- 
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