Hi, On Mon, Feb 11, 2008 at 06:54:10PM -0500, Andres Mejia wrote: > > Well, if you are sure that the target machines *do have inotify support* > > the only thing that could help is the config.log output of the failed > > configure process. > > The best thing toward logs are located at > http://buildd.debian.org/pkg.cgi?pkg=mediatomb .
That's the stdout of configure, what I am looking for is the config.log file that is created by configure during the process, but this is not there because everything is purged after the build. Any idea if we can get it? > > Then it should work; we do check the headers and then we run some small > > test code which is calling inotify_init(). If the inotify_init() function > > returns -1 (error) we will compile without inotify support; however - if > > the --enable-inotify parameter was specified configure will abort because > > it can not do what the user wanted. > > > > So the question: is inotify really working on those systems? > > I'm finding this behavior strange. Ubuntu accepted mediatomb into their > archive, yet now the powerpc architecture goes past the inotify check just > fine, but the i386 and amd64 architectures do not. Take a look at > https://launchpad.net/ubuntu/+source/mediatomb/0.10.0.dfsg1-1/ This is indeed very strange, it must be somehow related to the setup of the particular machine. What I see is that the default inotify header is not working, then we are retrying with our own and then it is failing. However, without seeing the config.log file I can not say anything... > I know for the case of the i386, I've been able to successfully build > packages > using pbuilder. Yes, I know, Leo has also been using pbuilder to create our custom .deb packages and we did not have any problems with inotify. Is the exact environment that those machines are using available somewhere? Can we reproduce the problem somehow? > Also, it looks like the Ubuntu buildd machines are giving a different error, > for architectures that run the inotify check sucessfully. Indeed, it seems that the build runs through but there is something wrong with the package, can't say much there either - I have no experience with .deb packages. Kind regards, Jin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
