On Friday 25 April 2008, Brad King wrote:
> This is the *exact* same problem as before. The error message is just
> more verbose. Now I need to know how to reproduce it. What source tree
> do I need to checkout?
I get this from svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs
> Please also se
Dirk Mueller wrote:
> On Monday 14 April 2008, Brad King wrote:
>
>> Okay, it doesn't matter how to reproduce it. The fix is the same.
>
> I've updated to RC9, and got a new problem:
>
> CMake Error at cmake/automoc/cmake_install.cmake:39 (FILE):
>
> file R
On Friday 25 April 2008, Dirk Mueller wrote:
> On Monday 14 April 2008, Brad King wrote:
> > Okay, it doesn't matter how to reproduce it. The fix is the same.
>
> I've updated to RC9, and got a new problem:
>
> CMake Error at cmake/automoc/cmake_install.cmake:39 (FILE):
> file RPATH_CHANGE could
On Monday 14 April 2008, Brad King wrote:
> Okay, it doesn't matter how to reproduce it. The fix is the same.
I've updated to RC9, and got a new problem:
CMake Error at cmake/automoc/cmake_install.cmake:39 (FILE):
file RPATH_CHANGE could not write new RPATH
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
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-
Dirk Mueller wrote:
> On Monday 14 April 2008, Brad King wrote:
>
>> CMake 2.6 comes with an ELF binary parser. It is used to change the
>> RPATH or RUNPATH of an existing binary before installation. This is
>> much faster than relinking with a new RPATH as was done by CMake 2.4
>> (relinking is
On Monday 14 April 2008, Brad King wrote:
> CMake 2.6 comes with an ELF binary parser. It is used to change the
> RPATH or RUNPATH of an existing binary before installation. This is
> much faster than relinking with a new RPATH as was done by CMake 2.4
> (relinking is still used on non-ELF syste
Brad King wrote:
>> By the way, this is not the first I've heard of this error. Other
>> people have run into it.
>
>Okay, but no one ever reported it to our bug tracker so I didn't know.
Yeah, I didn't hear from the first person either. He had just upgraded to
2.6 and was going to clean up and b
Thiago Macieira wrote:
> Brad King wrote:
>>> 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;
>>
Brad King wrote:
>> 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;
>
>CMake 2.6 comes with an ELF b
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-
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/
13 matches
Mail list logo
