Michael Biebl wrote: > Michael Ablassmeier wrote: >> hi Michael, >> >> On Wed, Jun 27, 2007 at 06:58:23PM +0200, Michael Biebl wrote: >>>> > /usr/include/netlink/rtnetlink-kernel.h:505: error: '__u64' does not >>>> name a type >>>> > /usr/include/netlink/rtnetlink-kernel.h:506: error: '__u64' does not >>>> name a type >>>> > /usr/include/netlink/rtnetlink-kernel.h:507: error: '__u64' does not >>>> name a type >>>> > /usr/include/netlink/rtnetlink-kernel.h:663: error: '__u64' does not >>>> name a type >>>> > /usr/include/netlink/rtnetlink-kernel.h:664: error: '__u64' does not >>>> name a type >>>> > /usr/include/netlink/rtnetlink-kernel.h:665: error: '__u64' does not >>>> name a type >>>> > make[4]: *** [knetworkmanager-devicestore.lo] Error 1 >>>> > make[4]: Leaving directory >>>> `/build/user/knetworkmanager-0.2~svn678822/obj-i486-linux-gnu/knetworkmanager/src' >>>> > make[3]: *** [all-recursive] Error 1 >>>> > make[3]: Leaving directory >>>> `/build/user/knetworkmanager-0.2~svn678822/obj-i486-linux-gnu/knetworkmanager' >>>> > make[2]: *** [all-recursive] Error 1 >>>> > make[2]: Leaving directory >>>> `/build/user/knetworkmanager-0.2~svn678822/obj-i486-linux-gnu' >>>> > make[1]: *** [all] Error 2 >>>> > make[1]: Leaving directory >>>> `/build/user/knetworkmanager-0.2~svn678822/obj-i486-linux-gnu' >>>> > make: *** [debian/stamp-makefile-build] Error 2 >>>> >>>> The Full Build log is available and can be viewed at: >>>> >>>> http://people.debian.org/~lucas/logs/2007/06/25/ >>> According to >>> http://buildd.debian.org/build.php?&pkg=knetworkmanager&ver=1%3A0.2%7Esvn678822-1&arch=amd64&file=log >>> >>> knetworkmanager has been successfully built on amd64. So I'm a bit >>> surprised, >>> that it fails for you. >>> Could you help me, investigate that? >> the rebuild mentioned above was done on i386, can you confirm its not >> failing for >> i386 too? > > Ah, I was fooled by this line: > Automatic build of knetworkmanager_1:0.2~svn678822-1 on > paraquad05.rennes.grid5000.fr by sbuild/amd64 0.55 > ^^^^^ > > The actual problem is very likely a bug in libnl. I had troubles compiling > knm, > so I added the patch debian/patches/02-linux_types.patch, which was supposed > to > work around the problem in libnl by adding a > > #include <linux/types.h> > > line to src/knetworkmanager-devicestore.cpp (as recommended by upstream). > linux/types.h is provided by linux-kernel-headers. > The package then compiles fine on my i386 laptop. If I switch to > linux-libc-dev > though, which replaces linux-kernel-headers, then the compilation also fails > on > my laptop. > > As on the above machine linux-libc-dev is installed, this explains, why it > fails > there. > > The question now is, if this is a problem within linux-libc-dev and how I can > fix that properly. Adding a build-depends on linux-kernel-headers does not > seem > to be a clean solution to me. >
What strikes me odd though, is that some buildds are obviously using linux-kernel-headers, and some linux-libc-dev. If those two packages lead to different build results, than that is very bad imho. Maybe I'm missing something... Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
