[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE-3.5.10+ FAM, INotify, DNotify
From:       James Richard Tyrer <tyrerj () acm ! org>
Date:       2008-09-18 5:13:33
Message-ID: 48D1E37D.3070704 () acm ! org
[Download RAW message or body]

James Richard Tyrer wrote:
> What is the status of file alteration monitoring in the KDE-3.5 BRANCH?
> 
> The last release of FAM was 2.7.0 in +/- 11/2003.  I obtained a DNotify 
> patch from a link at Linux From Scratch:
> 
> http://www.linuxfromscratch.org/blfs/downloads/6.1/fam-2.7.0-dnotify-1.patch
> 
> After 6.1, BLFS replaced it with Gamin.
> 
> I find that FAM will still compile with only minor tweaks to the Includes.
> 
> Should we continue to use FAM or should I install Gamin instead of FAM? 
>   Will KDE find this to use in place of FAM although FAM appears to be 
> found and KDELibs builds against it OK?
> 
> I presume that if I am using the DNotify pach that I shouldn't compile 
> KDELibs with: "--enable-dnotify".  It appears that: "--enable-inotify" 
> is the default.  And here I find a problem.  "config.log" says:
> 
> configure:55334: checking for Linux Inotify Notification
> configure:55439: result: no
> 
> I checked my Kernel configuration and it has:
> 
> CONFIG_DNOTIFY=y
> CONFIG_INOTIFY=y
> CONFIG_INOTIFY_USER=y
> 
> I have Kernel-2.6.25.4 and am upgrading.
> 
> so, it appears that I have a problem.  I will look at this in more 
> detail before I file a bug report.
> 
> Any suggestions?
> 
So, I have now upgraded the Kernel to 2.6.26.5 and GCC to 4.3.2 and not 
KDE finds INotify.  So, that problem solved except that I don't know the 
cause.

The question remains.  Do we need to continue to use the rather old FAM 
release?

-- 
JRT

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]