Version: (using KDE Devel) Installed from: Compiled sources Compiler: gcc 3.3.5 OS: Linux I don't entirely understand why this bug exists, but I've been able to work around it by doing the following. In the configure.in.in in the kscreensaver/kxsrun folder, I changed the first "XSCREENSAVER=NO" line to "XSCREENSAVER=", after looking at the output in the configure script and scratching my head for half an hour. Anyhow, I think the dual-use of the XSCREENSAVER variable was causing a glitch with the KDE_FIND macros. Hope to see a fix for this soon
Which distribution? Can you post the kdeartwork/config.log file?
no distribution, using kdesvn-build (on top of a gentoo system, already made sure the xscreensaver paths are right)...and the relevant lines of config.log read: configure:33194: checking for lib/xscreensaver/flame configure:33436: result: NO and after my patch it reads configure:33194: checking for lib/xscreensaver/flame configure:33436: result: /usr/X11R6/lib/xscreensaver/flame
Please attach the entire config.log, not a small part of it.
Created attachment 11939 [details] config.log
The same problem appears when I compile the latest trunk of kdeartwork on Fedora Core 4
The problem seems to be that the KDE_FIND_PATH() macro does nothing if the XSCREENSAVER variable is already defined. See bug 105748 comment #14.
*** This bug has been marked as a duplicate of 105748 ***