projectm version 2.0.1+dfsg-7 failed to build on amd64 with GCC-4.6/oneiric
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| projectM |
Unknown
|
Unknown
|
|||
| projectm (Debian) |
Fix Released
|
Unknown
|
|||
| projectm (Ubuntu) |
Fix Released
|
High
|
Alessio Treglia | ||
Bug Description
projectm version 2.0.1+dfsg-7 failed to build on amd64 with GCC-4.6/oneiric
Link to failed build: https:/
Details about the rebuild:
https:/
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'.
Excerpt 1574 lines into the build log:
make[3]: Entering directory `/build/
/usr/bin/cmake -E cmake_progress_
[ 94%] Building CXX object projectM-
cd /build/
/build/
/build/
make[3]: *** [projectM-
make[3]: Leaving directory `/build/
make[2]: *** [projectM-
make[2]: Leaving directory `/build/
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
*******
Build finished at 20110425-1744
FAILED [dpkg-buildpackage died]
Purging chroot-
Related branches
| Changed in projectm (Ubuntu): | |
| importance: | Undecided → High |
| Matthias Klumpp (ximion) wrote | #1 |
| Alessio Treglia (quadrispro) wrote | #2 |
| Changed in projectm (Ubuntu): | |
| assignee: | nobody → Alessio Treglia (quadrispro) |
| status: | New → Fix Committed |
| status: | Fix Committed → Fix Released |
| Changed in projectm (Debian): | |
| status: | Unknown → Fix Released |
Okay, how can
extern "C" VisPalette *lv_projectm_
{
return NULL;
}
be invalid? The method just returns a 0pointer, for VisPalette*, which definitely is valid and no "invalid conversion from 'void*' to 'VisPalette*'" - does someone have a clue why this happens?