Bug 109462

Summary:	configure fails to detect xscreensaver install
Product:	[Unmaintained] kscreensaver	Reporter:	Quinn Storm <livinglatexkali>
Component:	kxsrun	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	config.log

Description Quinn Storm 2005-07-22 13:14:48 UTC

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

Comment 1 Chris Howells 2005-07-22 13:29:28 UTC

Which distribution? Can you post the kdeartwork/config.log file?

Comment 2 Quinn Storm 2005-07-22 13:38:41 UTC

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

Comment 3 Chris Howells 2005-07-22 13:49:12 UTC

Please attach the entire config.log, not a small part of it.

Comment 4 Alexander Malashenko 2005-07-26 17:02:46 UTC

Created attachment 11939 [details]
config.log

Comment 5 Alexander Malashenko 2005-07-26 17:04:44 UTC

The same problem appears when I compile the latest trunk of kdeartwork on Fedora Core 4

Comment 6 Gregorio Guidi 2005-08-11 19:41:13 UTC

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.

Comment 7 Rex Dieter 2005-08-19 14:08:30 UTC


*** This bug has been marked as a duplicate of 105748 ***