kdelibs-4.2.2 and kdelibs-4.2.2-r1 fail to build because they try to build Windows-specific files which include windows.h (among other system-specific headers) which don't exist on Linux. cmake tries to build these Windows-specific files because at the beginning of the configuration process, it thinks that Q_WS_WIN is defined (build log attached). All other Qt and KDE packages do not think that it's defined. Only kdelibs-4.2.2 and kdelibs-4.2.2-r1 from the main portage tree are affected; the ebuild from the kde-testing overlay worked just fine. Reproducible: Always Steps to Reproduce:
Created attachment 188515 [details] build log for kdelibs-4.2.2-r1
-- Looking for Q_WS_X11 -- Looking for Q_WS_X11 - found -- Looking for Q_WS_WIN -- Looking for Q_WS_WIN - found -- Looking for Q_WS_QWS -- Looking for Q_WS_QWS - found -- Looking for Q_WS_MAC -- Looking for Q_WS_MAC - found Really i am not sure how did you managed to make this :D It is mutaly exclusive :D
Just ran into this problem again building kdelibs-4.2.4. I discovered that it's not a problem with kdelibs per se. It's a problem with building kdelibs using distcc. Running "pump emerge kdelibs" causes cmake to set those Q_WS_WIN, Q_WS_QWS, and Q_WS_MAC symbols, causing kdelibs build to fail.
I've been using distcc to compile kde4 for some time now.. can you please verify your distcc configuration and try with kde 4.3.0? Thanks :)
No problems with the following: distcc-3.1-r4 cmake-2.6.4-r2 kdelibs-4.3.0
Sorry to reopen, but I'm still having the problem. It's been a problem with kdelibs-4.3.1, -4.3.1-r1, and -4.3.2. Any suggestions what I should try next?
As someone said, it's most certainly your distcc configuration that -DLINUX (or similar definitions) are not appended to preprocessor thus giving kdelibs no means to detect destination environment thus trying to compile KDE Windows code. I'm afraid you're on your on in this case.
(In reply to comment #6) > Sorry to reopen, but I'm still having the problem. It's been a problem with > kdelibs-4.3.1, -4.3.1-r1, and -4.3.2. Any suggestions what I should try next? > emerge --info missing.
i'm closing this, please try with 4.4.2 and reopen if it is still an issue
Hmmm, I had no problem with kdelibs-4.3.* and distcc-3.1-r4, but just ran into this bug with kdelibs-4.4.4 and unpatched distcc svn-719. For starters I can point out that it only happens in pump mode, which makes sense since it appears to be a preprocessing problem. I'll comment again later when I get a chance to test with the distcc version in portage.
