13 messages in org.kde.kde-buildsystemproblem 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:problem with cmake 2.6RC6 and KDE 4Actions...
From:Dirk Mueller (muel@kde.org)
Date:Apr 14, 2008 2:54:11 am
List:org.kde.kde-buildsystem

Hi,

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;

how can I get rid of that? this is KDE trunk, configured with:

cmake -DKDE4_BUILD_TESTS=ON -DCMAKE_INSTALL_PREFIX=/opt/testing
-DCMAKE_BUILD_TYPE=release

a slightly related and annoying note: for some projects (e.g. strigi) it writes an empty rpath into the binaries during installation instead of removing the rpath. that breaks certain checks and is dangerous, as some ld.so versions interpret empty as "current directory" which allows trivially to hijack applications by e.g. adding a hacked libc.so.6 to the start up directory.

Thanks, Dirk

_______________________________________________ Kde-buildsystem mailing list Kde-@kde.org https://mail.kde.org/mailman/listinfo/kde-buildsystem