widelands version 1:15-2 failed to build on i386
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Won't Fix
|
Undecided
|
Unassigned | ||
widelands (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Fix Released
|
High
|
Unassigned |
Bug Description
widelands version 1:15-2 failed to build on i386
Link to failed build: https:/
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1880 lines into the build log:
/build/
/build/
/build/
/build/
/build/
make[4]: *** [src/editor/
make[4]: Leaving directory `/build/
make[3]: *** [src/editor/
make[3]: Leaving directory `/build/
make[2]: *** [all] Error 2
make[2]: Leaving directory `/build/
make[1]: *** [override_
make[1]: Leaving directory `/build/
make: *** [binary] Error 2
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary gave error exit status 2
*******
Build finished at 20110408-1802
FAILED [dpkg-buildpackage died]
Purging chroot-
Changed in widelands (Ubuntu): | |
importance: | Undecided → High |
tags: | added: oneiric |
Changed in widelands (Ubuntu): | |
milestone: | none → oneiric-alpha-1 |
I discovered this in the Ubuntu bug tracker, and just wanted to check if this is something which have already been addressed upstream. I briefly checked the file mentioned in the error, but from what I can see it has been updated, probably fixing this issue. (And I was able to successfully compile latest version of trunk on Ubuntu Natty earlier today.) Was that change done due to similar errors happening?
I guess the issue is still present for build15/Ubuntu, though, so I guess that part of the bug report should be left alone regardless of what the situation is upstreams.