sprng version 2.0a-8 failed to build on armel

Bug #791238 reported by Ricardo Salveti on 2011-06-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sprng (Ubuntu)
Undecided
Colin Watson

Bug Description

sprng version 2.0a-8 failed to build on armel
Link to failed build: https://launchpad.net/ubuntu/+source/sprng/2.0a-8/+build/2513292

Direct link to the build log: https://launchpad.net/ubuntu/+source/sprng/2.0a-8/+build/2513292/+files/buildlog_ubuntu-oneiric-armel.sprng_2.0a-8_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 484 lines into the build log:

dh_testroot
dh_clean -k
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs usr/lib usr/include/sprng
make -n install
make[1]: Entering directory `/build/buildd/sprng-2.0a'
install -d /usr/lib
install -p SRC/../lib/libsprng.a /usr/lib
install -d /usr/include
install -p SRC/../include/* /usr/include
make[1]: Leaving directory `/build/buildd/sprng-2.0a'
cp -vax lib/libsprng.so.2.0 /build/buildd/sprng-2.0a/debian/libsprng2/usr/lib/
cp: cannot stat `lib/libsprng.so.2.0': No such file or directory
make: *** [install] Error 1
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary-arch gave error exit status 2
******************************************************************************
Build finished at 20110519-1959
FAILED [dpkg-buildpackage died]
Purging chroot-autobuild/build/buildd/sprng-2.0a

Related branches

Colin Watson (cjwatson) on 2012-04-19
Changed in sprng (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
status: New → In Progress
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sprng - 2.0a-8ubuntu1

---------------
sprng (2.0a-8ubuntu1) precise; urgency=low

  * Use -Wa,-mimplicit-it=thumb on armel as well for now, since Ubuntu's
    armel requires Thumb-2 interworking (LP: #791238).
 -- Colin Watson <email address hidden> Thu, 19 Apr 2012 16:41:25 +0100

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

Other bug subscribers