Source: nbtk Version: 1.2.3-1 Severity: serious Tags: squeeze sid User: [email protected] Usertags: qa-ftbfs-20100410 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > CC nbtk_create_image_cache-nbtk-create-image-cache.o > LINK nbtk-create-image-cache > make[4]: Leaving directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/nbtk' > make[3]: Leaving directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/nbtk' > Making all in data > make[3]: Entering directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/data' > Making all in style > make[4]: Entering directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/data/style' > Generating .gitignore > make[4]: Leaving directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/data/style' > Generating .gitignore > make[3]: Leaving directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/data' > Making all in tests > make[3]: Entering directory > `/build/user-nbtk_1.2.3-1-amd64-mf5UtO/nbtk-1.2.3/tests' > CC > LINK test-buttons > ../nbtk/.libs/libnbtk-gtk-1.2.so: undefined reference to `GTK_WIDGET_DRAWABLE' > ../nbtk/.libs/libnbtk-gtk-1.2.so: undefined reference to `GTK_WIDGET_STATE' > ../nbtk/.libs/libnbtk-gtk-1.2.so: undefined reference to `GTK_WIDGET_VISIBLE' > ../nbtk/.libs/libnbtk-gtk-1.2.so: undefined reference to `GTK_WIDGET_MAPPED' > collect2: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2010/04/10/nbtk_1.2.3-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | [email protected] http://www.lucas-nussbaum.net/ | | jabber: [email protected] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
