qtmir rebuild fails with "assertion fail ../../bfd/elf32-i386.c:5245"

Bug #1510067 reported by Michał Sawicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
binutils (Ubuntu)
Fix Released
Undecided
Matthias Klose
qtmir (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Trying to rebuild qtmir in xenial with new binutils results in:

/usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.25.51.20151022 assertion fail ../../bfd/elf32-i386.c:5245

See i386 failures in autopkgtest:

http://autopkgtest.ubuntu.com/packages/q/qtmir/xenial/i386/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: binutils 2.25.51.20151022-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
CurrentDesktop: Unity
Date: Mon Oct 26 13:19:10 2015
Dependencies:
 gcc-5-base 5.2.1-22ubuntu5
 libc6 2.21-0ubuntu4
 libgcc1 1:5.2.1-22ubuntu5
 zlib1g 1:1.2.8.dfsg-2ubuntu4
SourcePackage: binutils
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

binutils 2.25.51.20151022-0ubuntu3 has been uploaded with an upstream fix for this issue. However, while it fixed the qtmir autopkgtest (http://autopkgtest.ubuntu.com/packages/q/qtmir/xenial/i386/), the fwupdate package is still failing to build (https://launchpad.net/ubuntu/+source/fwupdate/0.4+git20151015.081427-0ubuntu3/+build/8194112).

Changed in binutils (Ubuntu):
assignee: nobody → Matthias Klose (doko)
Changed in qtmir (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package binutils - 2.25.51.20151022-0ubuntu3

---------------
binutils (2.25.51.20151022-0ubuntu3) xenial; urgency=medium

  * Fix PR ld/19171, taken from the trunk. LP: #1510067.

 -- Matthias Klose <email address hidden> Mon, 26 Oct 2015 18:17:45 +0200

Changed in binutils (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.