Hi,
On Wed, Feb 03, 2010 at 10:12:08PM +0100, Mehdi wrote:
I'm not sure if Leo already told you this, but here's a bug asking for
mediatomb not to use an embedded prototype.js.
I've already tried using the prototype.js delivered in Debian (version
1.6.0.2). It's giving me problems
On Tue, Feb 12, 2008 at 10:40:20PM -0500, Andres Mejia wrote:
Possibly an oldish one, but it shouldn't matter. Whether the kernel
supports inotify should be checked at runtime, not build time.
Well, this makes sense. I could fix this for the build time. Does mediatomb
already check for
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
On Mon, Feb 11, 2008 at 01:41:03PM -0500, Andres Mejia wrote:
do not pass the --enable-inotify parameter to the configure script;
presence of inotify will be detected automatically, if not available it
will be disabled on the fly. However, when the --enable-inotify parameter
is passed by
Hi,
I'm one of the authors of MediaTomb, here is some info on this:
do not pass the --enable-inotify parameter to the configure script; presence
of inotify will be detected automatically, if not available it will be disabled
on the fly. However, when the --enable-inotify parameter is passed by
5 matches
Mail list logo
