Re: [Licq-devel] compiling qt-gui4

M Wedin <[email protected]> Thu, 18 Mar 2010 02:23:51 +0100
Newsgroups gmane.network.licq.devel
Message-ID <[email protected]>
2010/3/17 Erik Johansson <[email protected]>:
> On Sun, Mar 14, 2010 at 23:25, M Wedin <[email protected]> wrote:
>> The second part was good until "# make install". It bailed with:
>> ---------------------------------
>> -- Installing: /usr/local/lib/licq/licq_qt4-gui.so
>> -- Removed runtime path from "/usr/local/lib/licq/licq_qt4-gui.so"
>> CMake Error at cmake_install.cmake:50 (FILE):
>> =A0file Internal CMake error when trying to open file:
>> =A0/mnt/home/wed/targz/licq-1.3.8/plugins/qt4-gui/build/install_manifest=
.txt
>> =A0for writing.
>
> Sounds like a cmake bug. Which cmake version do you have?

$ cmake
cmake version 2.6-patch 2

>> I then moved the build directory to my local home, instead of the
>> NFS-mounted one. Still had problems, so I brought the original tar.gz
>> to the local home and unpacked it there. I didn't redo the licq part,
>> only the qt-gui. Seemingly, all went well.
>
> Build directories can't be moved. They use absolute paths to refer to fil=
es.

Glad to learn that, as I really feel that the workstation should be
rather empty apart from the OS.

>> Just figured you might want to know it has been built successfully on
>> Slackware. Qt and Qt-devel is provided for by default. And that there
>> might be an issue with remotely attached directories.
>
> Good to know, thanks. If you have the time, it would be interesting to
> know how well the current trunk builds on slackware.

I have to confess. I'm fairly new to Slackware and have reinstalled
the entire system a few times since then. At this time, Pidgin is a
substitute (not a worthy one). I will backup the system before I start
fiddling again.


Wedin