FTCBFS: Cross build calls wrong-arch gcc

Bug #963060 reported by Marcin Juszkiewicz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libbsd (Debian)
Fix Released
Unknown
libbsd (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

Is debian/patches/do-not-hardcode-gcc necessary at all? Variable initialisations like this in make are overridable on make's command line, so your change to debian/rules should be sufficient without that additional patch.

Revision history for this message
Colin Watson (cjwatson) wrote :

(Also I don't think you need to export DEB_HOST_GNU_TYPE.)

Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

Right, got rid of patch and export. Attached clean debdiff

Changed in libbsd (Ubuntu):
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Steve Langasek (vorlon)
Changed in libbsd (Ubuntu):
importance: Undecided → Medium
tags: added: rls-mgr-p-tracking
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libbsd - 0.3.0-1build2

---------------
libbsd (0.3.0-1build2) precise; urgency=low

  * Fixed cross building - LP: #963060
 -- Marcin Juszkiewicz <email address hidden> Fri, 30 Mar 2012 11:05:14 +0300

Changed in libbsd (Ubuntu):
status: New → Fix Released
Revision history for this message
Wookey (wookey) wrote :

This package still doesn't build correctly due to using wrong-arch gcc. See http://people.linaro.org/~wookey/buildd/precise/sbuild-ma/libbsd_0.3.0-2-precise-ma-cross-armel-20120410-023821.37273.log

Something is wrong with the fix that has been applied

Revision history for this message
Steve Langasek (vorlon) wrote :

Perhaps this is because the previous upload used a wrong version number? 1build2 indicates a no-change rebuild, which means the archive auto-sync would happily clobber it with a new version from Debian; and the new build log is for a -2 version, suggesting this is what happened.

Changed in libbsd (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Colin Watson (cjwatson) wrote :

Indeed. Reuploaded to quantal with a correct version number.

Changed in libbsd (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libbsd - 0.3.0-2ubuntu1

---------------
libbsd (0.3.0-2ubuntu1) quantal; urgency=low

  * Fixed cross building - LP: #963060
 -- Marcin Juszkiewicz <email address hidden> Fri, 27 Apr 2012 13:40:23 +0100

Changed in libbsd (Ubuntu):
status: In Progress → Fix Released
Changed in libbsd (Debian):
status: Unknown → Fix Released
Changed in libbsd (Debian):
status: Fix Released → New
Changed in libbsd (Debian):
status: New → Fix Released
Changed in libbsd (Ubuntu):
assignee: Canonical Foundations Team (canonical-foundations) → nobody
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.