13 messages in org.kde.kde-buildsystemRe: problem with cmake 2.6RC6 and KDE 4
FromSent OnAttachments
Dirk MuellerApr 14, 2008 2:54 am 
Brad KingApr 14, 2008 6:15 am 
Thiago MacieiraApr 14, 2008 6:31 am 
Brad KingApr 14, 2008 6:42 am 
Thiago MacieiraApr 14, 2008 6:53 am 
Dirk MuellerApr 14, 2008 7:14 am 
Brad KingApr 14, 2008 7:36 am 
Brad KingApr 14, 2008 10:25 am 
Brad KingApr 14, 2008 12:06 pm 
Dirk MuellerApr 25, 2008 11:07 am 
Alexander NeundorfApr 25, 2008 11:27 am 
Brad KingApr 25, 2008 12:17 pm 
Dirk MuellerApr 29, 2008 6:52 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: problem with cmake 2.6RC6 and KDE 4Actions...
From:Brad King (brad@kitware.com)
Date:Apr 14, 2008 12:06:19 pm
List:org.kde.kde-buildsystem

Brad King wrote:

Dirk Mueller wrote:

I've switched to cmake 2.6 for dashbot (http://ktown.kde.org/~dirk/dashboard/). The problem I have now is this:

CMake Error at cmake/automoc/cmake_install.cmake:39 (FILE): file CHRPATH could not write new RPATH "/opt/testing/lib" to the file "/var/tmp/kdelibs-796689-build/opt/testing/bin/kde4automoc": No valid ELF RPATH entry exists in the file;

I'm having trouble reproducing this. [snip] How did you get to the situation reporting the error? Was this a completely clean build and install tree, or was it an existing tree from CMake 2.4 that was upgraded?

Okay, it doesn't matter how to reproduce it. The fix is the same.

I've committed changes to CMake HEAD in CVS to address this problem and the one about removing the RPATH entry. Before installing CMake now checks if there is an existing binary that has the wrong RPATH and removes it. That will make sure the new copy from the build tree gets installed and subsequently patched to update or remove the RPATH entry.

These fixes will be in the 2.6 release.

-Brad