Version: (using Devel) Compiler: gcc-4.1.2 OS: Linux Installed from: Compiled sources When compiling KDE-base, some files are looking for Phonon header files. The problem is that they are looking for them at the wrong place. As an example, kdebase/workspace/kcontrol/access/kaccess.h is looking for <Phonon/MediaObject>, but phonon installs this file in /usr/include/KDE/Phonon/MediaObject. So, if I'm right (I'm not coder at all), the line should be : #include <KDE/Phonon/MediaObject> Of course, as it is now, the compilation fails.
No, it is fine as it is. CMake should automatically add -I/usr/include/KDE to the compiler command line so that the compiler can find the file. If you are compiling kdebase from trunk and it fails because of that, it probably means that the cmake scripts are broken at the moment. Please be patient.
I updated KDE SVN as well as Cmake to 2.6.1. But I still have this issue with KDE-base.
I added /usr/include/KDE tu cmake include path in .bashrc. It works for the part I reported, but kdebase still doesn't compile. The error is still linked to Phonon. Since the console output is a little long, I create an attachement.
Created attachment 27193 [details] Console output of the compilation failure
did you compile kdelibs from the same version from scratch? we've added compatibility include paths for this phonon include problem for KDE 4.1. are you trying to build trunk/ or KDE 4.1?
I'm trying to build trunk. Also, I'm always updating kdelibs and kdebase at the same time. I tried to update from scratch 2 days ago. I'll try that again today.
Please also try to update kdesupport. Phonon resides in kdesupport, not in kdelibs. Also, in case you are using phonon from qt, stop using it. And if you need help, ask in irc or in forums. This is not a user support area, this is a bugtracker, and I am pretty sure this is not a bug. Judging from the fact that kdebase builds for everybody else except you, you must be doing something wrong. I will close this bug again now. If you can confirm with somebody else that this is a bug in the build system and/or you have facts that prove it, please reopen.