PyQt5 installation error at ENSEEIHT

[mpizenberg]

I have tried to install PyQt5 in my home with a Python3 virtual environement.

First I setup a virtual env in my nosave directory :

virtualenv --python=python3 env
source env/bin/activate  
python --version

Then I installed sip (needed for PyQt). I needed to change the directory where the SIP header file will be installed with the -e option :

cd sip-4.16.4/
python configure.py -e /home/mpizenbe/nosave/env/include
make
make install

It worked since the following commands in the python interpreter work :

import sip  
sip.SIP_VERSION_STR

Until now everything went right but at the PyQt5 installation step that is when I have errors.

cd ../PyQt-gpl-5.4/
python configure.py --sip-incdir=/home/mpizenbe/nosave/env/include --verbose

It returns the following errors :

Querying qmake about your Qt installation...
Determining the details of your Qt installation...
/home/mpizenbe/nosave/Qt5/5.4/gcc_64/bin/qmake -o qtdetail.mk qtdetail.pro
Cannot read /home/.qmake.super: No such file or directory
Error processing project file: qtdetail.pro
Error: Failed to determine the detail of your Qt installation. Try again using
the --verbose flag to see more detail about the problem.

It seems that that error is due to the Qt5 home installation and I do not find anywhere someone that was blocked by that qmake error. However the Qt5 home installation seems to work (at least partially) since qmlscene works for example.

[fabiencastan]

https://github.com/pyqt/python-qt5/wiki/Compiling-PyQt5-on-Ubuntu-12.04

You need to set the --qmake option.

[mpizenberg]

I did it first time but I don't know why qmake crashes as soon as it is used a second time. For example here I tried on another pc at ENSEEIHT and as qmake is called many times in the configure.py script at the second it crashes :

save/env/include --qmake=/home/mpizenbe/nosave/Qt5/5.4/gcc_64/bin/qmake --verbose
Querying qmake about your Qt installation...
Determining the details of your Qt installation...
/home/mpizenbe/nosave/Qt5/5.4/gcc_64/bin/qmake -o qtdetail.mk qtdetail.pro
make -f qtdetail.mk
g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIE -DQT_NO_DEBUG -DQT_CORE_LIB -I../Qt5/5.4/gcc_64/mkspecs/linux-g++ -I. -I../Qt5/5.4/gcc_64/include -I../Qt5/5.4/gcc_64/include/QtCore -I. -o qtdetail.o qtdetail.cpp
g++ -Wl,-O1 -Wl,-rpath,/home/mpizenbe/nosave/Qt5/5.4/gcc_64 -Wl,-rpath,/home/mpizenbe/nosave/Qt5/5.4/gcc_64/lib -o qtdetail qtdetail.o   -L/home/mpizenbe/nosave/Qt5/5.4/gcc_64/lib -lQt5Core -lpthread 
./qtdetail
This is the GPL version of PyQt 5.4 (licensed under the GNU General Public
License) for Python 3.2.3 on linux2.
Type 'L' to view the license.
Type 'yes' to accept the terms of the license.
Type 'no' to decline the terms of the license.
Do you accept the terms of the license? yes
Found the license file pyqt-gpl.sip.
Checking to see if the QtGui module should be built...
/home/mpizenbe/nosave/Qt5/5.4/gcc_64/bin/qmake -o cfgtest_QtGui.mk cfgtest_QtGui.pro
Cannot read /home/.qmake.super: No such file or directory
Error processing project file: cfgtest_QtGui.pro
Checking to see if the QtHelp module should be built...
...

...
Error: /home/mpizenbe/nosave/Qt5/5.4/gcc_64/bin/qmake failed to create a
makefile from PyQt5.pro.

[fabiencastan]

It's strange that it looks into /home and not in your real home: /home/.qmake.super.
Is your home var correct? echo $HOME

Could you send the full command line and full output?

[mpizenberg]

Yes, the echo $HOME command returns to me /home/mpizenbe :

(env)mpizenbe@stones:~/nosave/PyQt-gpl-5.4$ echo $HOME
/home/mpizenbe

[mpizenberg]

And I don't know if it matters but I don't have any file called .qmake.super in my home either.

[simogasp]

Pierre Gambarotto m'a suggéré d'utiliser proot (/home/gamba/public/prrot.md) dans ton nosave, ça permet de utiliser le gestionnaire de paquets apt pour installer le biblioteques (bof, j'ai pas trop compris comment ça marche...)

[KtorZ]

Voui, j'ai passé un bon bout de temps la journée de mardi à me battre avec proot et une installation dans le répertoire nosave. Le problème, c'est que dans cet environnement particulier, OpenGL ne fonctionne plus, et impossible d'installer quoi que ce soit au niveau des drivers sans devoir agir sur le système initial (impossible sans accés root). Bref, du coup, on peut faire fonctionner les scènes QML de façon indépendante via les exécutables fournis par Qt, on peut, sur le nosave, executer des programmes Python utilisant PyQt5; Mais on ne peut pas instancier de vues QML depuis Python avec PyQt5 sans recevoir des belles erreurs de la part d'openGL. Pour l'instant, on développe donc les parties séparemment, et on test sur des ordinateurs personnels.