Bug 168650 – different compilation configuration in split versus monolithic kde ebuild

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Paul B. Henson 2007-02-27 22:47:12 UTC]

I have KDE 3.5.5 installed using split ebuilds. I was trying to resolve a problem I was having with x11vnc, kdesktop, and DPMS when I realized that kdesktop did not appear to be compiled with DPMS support turned on.

I unpacked and compiled the split ebuild, and changed to the compilation directory /var/tmp/portage/kdesktop-3.5.5/work/kdesktop-3.5.5, and ran "grep DPMS config.h", which resulted in no output.

I then unpacked and compiled the monolithic kdebase-3.5.5-r3 ebuild, changed to the compilation directory /var/tmp/portage/kdebase-3.5.5-r3/work/kdebase-3.5.5, running the same command resulted in:

/* Define if you have DPMS support */
#define HAVE_DPMS 1
/* Define if you have the DPMSCapable prototype in <X11/extensions/dpms.h> */
#define HAVE_DPMSCAPABLE_PROTO 1
/* Define if you have the DPMSInfo prototype in <X11/extensions/dpms.h> */
#define HAVE_DPMSINFO_PROTO 1

To doublecheck, I edited the xautolock.cc file in both compilation directories, and added the line "#error DPMS" inside of an "#ifdef HAVE_DPMS" block. As expected, the split ebuild continued to compile fine, whereas compilation of xautolock.cc in the monolithic ebuild failed with a preprocessor error, confirming that the split ebuild was being compiled with a different configuration than monolithic ebuild.

This seems inconsistent and undesirable? Running diff on the two config.h files shows there are a large number of differences. I'm not sure how many are relevant, but at the very least one results in a different configuration of kdesktop.


Reproducible: Always

Steps to Reproduce:

[Comment 1 Jorge Manuel B. S. Vicetto (RETIRED) 2007-09-10 01:14:29 UTC]

Please try this with kde-3.5.7. If this is still an issue, reopen the bug.