You are not logged in.
Since upgrading my system yesterday Cmake doesn't seem to be working correctly. It doesn't seem to be finding files that a build requires, even though they are in /usr/include. I've been able to reproduce this on a few packages, now. I've just produced it again, while trying to compile compiz from sources;
[ninez@ninez compiz-libcompizconfig]$ build-compiz
-- The C compiler identification is GNU 4.7.0
-- The CXX compiler identification is GNU 4.7.0
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26")
CMake Error at CMakeLists.txt:11 (include):
include could not find load file:
CompizCommon
CMake Error at CMakeLists.txt:12 (include):
include could not find load file:
CompizPackage
-- checking for module 'protobuf'
-- found protobuf, version 2.4.1
-- Looking for sys/inotify.h
-- Looking for sys/inotify.h - found
CMake Error at CMakeLists.txt:127 (compiz_pkg_check_modules):
Unknown CMake command "compiz_pkg_check_modules".
-- Configuring incomplete, errors occurred!
NOTE: Before the upgrade, compiling with cmake worked just fine, including this very source code.
I'll see if i can remember what other packages were giving me grief, and post them as well. ~ if i manually specify the complete 'include' path for things like CompizCommon (in CMakelists.txt) , i do get past the issue. However, like i said - this wasn't a problem before upgrading, and i shouldn't have to manually put in the full paths. something is wrong.
any help is appreciated
cheerz
Last edited by triplesquarednine (2012-04-25 21:26:27)
Offline
Getting the exact same problem, with the same source. Although I never used cmake before trying this.
Any help is appreciated.
Offline
Getting the exact same problem, with the same source. Although I never used cmake before trying this.
Any help is appreciated.
As of yet, i haven't figured it out.
I had hoped that your post, might have been someone who knows what is going on.
oh well. I guess i'll have to have another stab at it.
cheerz
Offline
Looking at the changelog for cmake 2.8.8, it could well be that it is working as intended.
Noah, downgrading to cmake 2.8.7 is quick way around the problem.
Last edited by rufflove (2012-04-25 13:34:36)
"Its too big and too slow"
Offline
Looking at the changelog for cmake 2.8.8, it could well be that it is working as intended.
Noah, downgrading to cmake 2.8.7 is quick way around the problem.
Thanks for this, Rufflove.
I just got in the door, so i think i'll downgrade cmake.
cheerz
EDIT: Yup, That's seems to do the trick. 2.8.7 works OOTB, 2.8.8 does not.
I've also mentioned this to Sam. (in case, it turns out that they need to change some stuff for that version).
marked [SOLVED]
Last edited by triplesquarednine (2012-04-25 17:54:53)
Offline
I posted a bug a couple days back, and Daniel marked it for 0.9.7.2. I went back to cmake 2.8.7 as soon as I realised I'd have to set all the paths manually...
"Its too big and too slow"
Offline
Just for anyone who stumbles by thread.
This was a bug in Cmake, but it has now been fixed upstream.
cheerz
Offline