Andres Mejia wrote on 12/02/2008 05:45:
I've investigated this some more and found that the inotify-tools package fails the test to see if sys/inotify.h actually works for the powerpc and ia64 architectures as well, yet the build continues for that package, unlike in mediatomb. Here's the difference between the two packages' configure.ac
[...]
Perhaps I'm wrong about what kernel each buildd machine is using. This would explain why this check fails on these architectures, but I can't find a straight answer. Sven, do you know the answer to this?
No, sorry. Best bet IMHO is to contact the porters for the given architectures and ask for their help:
[EMAIL PROTECTED] [EMAIL PROTECTED] And the buildd admins for those architectures (if the porters can't help): [EMAIL PROTECTED] [EMAIL PROTECTED]
The buildd machines use sbuild, which uses debootstrap for creating the chroot environment, so I'm sure at least the latest version of linux-libc-dev is installed. In case some buildd machines don't support inotify, the check to see if inotify works should be left out.
Probably. Though the buildds should support the latest _stable_ kernel with the latest _unstable_ chroot environment. And since 2.6.18 supports inotify, I fail to see why this doesn't work on the architectures named. But I'm unsure wether inotify is supported on all Linux architectures (though I'm 90% certain it is, I don't see anything hardware specific in there).
cu, Sven
signature.asc
Description: OpenPGP digital signature
