On Friday 07 January 2011 06:41:51 Renato Araujo Oliveira Filho
wrote:
> The PySide team is happy to announce the third beta release
> of PySide
Thank you for the release - obrigado! I've tried to install the
PySide beta3 to a VM, where I had installed a beta2 a few days
ago. It appears that after some 150 mins the compilation was
complete, but the installation failed with the following few
messages:
[100%] Built target testbinding
Install the project...
-- Install configuration: "Release"
-- Installing: /usr/local/include/PySide/dynamicqmetaobject.h
CMake Error at libpyside/cmake_install.cmake:36 (FILE):
file INSTALL cannot copy file
"/home/ak/sandbox/apiextractor/build/generatorrunner/build/shiboken/build/pyside/libpysbject.h"
to "/usr/local/include/PySide/dynamicqmetaobject.h".
Call Stack (most recent call first):
cmake_install.cmake:37 (INCLUDE)
make: *** [install] Error 1
[sudo] password for ak:
The password could not be entered, as the input line seemed
"frozen". I ended this assembly by having to switch off the
console by clicking on the (x) in the top right hand corner.
The OS was kubuntu 10.10 (i386), the VM is a small one with 512
MB RAM, 1 Processor,
After the attempted installation, the version information
suggested that the old (beta2) version was still active:
Python 2.6.6 (r266:84292, Sep 15 2010, 15:52:39)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more
information.
>>> import PySide
>>> print PySide.__version__
1.0.0
>>> print PySide.__version_info__
(1, 0, 0)
>>>
Question is: after a failed installation, it would appear the
the compilation is complete. Is it practical to use (somehow)
the compiled packages and resume installation only?
OldAl.
--
Algis
http://akabaila.pcug.org.au
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
