| View previous topic :: View next topic |
| Author |
Message |
melts
n00b
Joined: 21 Feb 2004
Posts: 53
|
 Posted: Tue Sep 16, 2014 8:49 am Post subject: emerging dev-python/pyside-tools-0.2.14 |
 |
|
Hi
Having an issue emerging dev-python/pyside-tools-0.2.14 - it appears to want to pull in Python 3.2 libraries but they aren't available. I can post the full build logs and the like but I thought the output from build and the USE flags of the related packages tell the story just as well (and faster).
These are the the USE flags of the packages related
| Code: | [ebuild R ] dev-python/pyside-1.1.2-r1 USE="X declarative help kde multimedia opengl phonon script scripttools sql svg webkit xmlpatterns {-test}" PYTHON_TARGETS="python2_7 (-python3_2)" 0 kB
[ebuild R ] dev-python/PyQt4-4.10.3-r2 USE="X dbus declarative designer doc examples help kde multimedia opengl phonon script scripttools sql svg webkit xmlpatterns -debug" PYTHON_TARGETS="python2_7 python3_3 (-python3_2)" 0 kB
[ebuild N ] dev-python/pyside-tools-0.2.14 USE="{-test}" 0 kB |
and the emerge build output;
| Code: | >>> Emerging (1 of 1) dev-python/pyside-tools-0.2.14
* pyside-tools-0.2.14.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking pyside-tools-0.2.14.tar.bz2 to /var/tmp/portage/dev-python/pyside-tools-0.2.14/work
>>> Source unpacked in /var/tmp/portage/dev-python/pyside-tools-0.2.14/work
>>> Preparing source in /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14 ...
* Applying 0.2.13-fix-pysideuic-test-and-install.patch ... [ ok ]
* Preparation of dev-python/pyside-tools-0.2.14 with CPython 2.7...
* Preparation of dev-python/pyside-tools-0.2.14 with CPython 3.2...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14 ...
* Configuration of dev-python/pyside-tools-0.2.14 with CPython 2.7...
>>> Working in BUILD_DIR: "/var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-2.7"
cmake --no-warn-unused-cli -C /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-2.7/gentoo_common_config.cmake -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr -DPYTHON_BASENAME=-python2.7 -DPYTHON_SUFFIX=-python2.7 -DSITE_PACKAGE=/usr/lib64/python2.7/site-packages -DBUILD_TESTS=OFF -DCMAKE_BUILD_TYPE=Gentoo -DCMAKE_INSTALL_DO_STRIP=OFF -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-2.7/gentoo_rules.cmake /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-2.7
Not searching for unused variables given on the command line.
loading initial cache file /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-2.7/gentoo_common_config.cmake
-- The C compiler identification is GNU 4.5.3
-- The CXX compiler identification is GNU 4.5.3
-- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc
-- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/x86_64-pc-linux-gnu-g++
-- Check for working CXX compiler: /usr/bin/x86_64-pc-linux-gnu-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found PythonInterp: /usr/bin/python (found version "2.7.6")
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/bin/qmake (found suitable version "4.8.5", minimum required is "4.5.0")
-- <<< Gentoo configuration >>>
Build type Gentoo
Install path /usr
Compiler flags:
C -O3 -pipe -funroll-loops
C++ -O3 -pipe -funroll-loops
Linker flags:
Executable -Wl,-O1 -Wl,--as-needed
Module -Wl,-O1 -Wl,--as-needed
Shared -Wl,-O1 -Wl,--as-needed
-- Configuring done
-- Generating done
-- Build files have been written to: /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-2.7
* Configuration of dev-python/pyside-tools-0.2.14 with CPython 3.2...
>>> Working in BUILD_DIR: "/var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-3.2"
cmake --no-warn-unused-cli -C /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-3.2/gentoo_common_config.cmake -G Unix Makefiles -DCMAKE_INSTALL_PREFIX=/usr -DPYTHON_BASENAME=-python3.2 -DPYTHON_SUFFIX=-python3.2 -DSITE_PACKAGE=/usr/lib64/python3.2/site-packages -DBUILD_TESTS=OFF -DCMAKE_BUILD_TYPE=Gentoo -DCMAKE_INSTALL_DO_STRIP=OFF -DCMAKE_USER_MAKE_RULES_OVERRIDE=/var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-3.2/gentoo_rules.cmake /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-3.2
Not searching for unused variables given on the command line.
loading initial cache file /var/tmp/portage/dev-python/pyside-tools-0.2.14/work/pyside-tools-0.2.14-3.2/gentoo_common_config.cmake
-- The C compiler identification is GNU 4.5.3
-- The CXX compiler identification is GNU 4.5.3
-- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc
-- Check for working C compiler: /usr/bin/x86_64-pc-linux-gnu-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/x86_64-pc-linux-gnu-g++
-- Check for working CXX compiler: /usr/bin/x86_64-pc-linux-gnu-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Found PythonInterp: /usr/bin/python (found version "3.2.3")
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
-- Found Qt4: /usr/bin/qmake (found suitable version "4.8.5", minimum required is "4.5.0")
CMake Error at /usr/lib64/cmake/PySide-1.1.2/PySideConfig.cmake:5 (include):
include could not find load file:
/usr/lib64/cmake/PySide-1.1.2/PySideConfig-python3.2.cmake
Call Stack (most recent call first):
CMakeLists.txt:7 (find_package)
-- <<< Gentoo configuration >>>
Build type Gentoo
Install path /usr
Compiler flags:
C -O3 -pipe -funroll-loops
C++ -O3 -pipe -funroll-loops
Linker flags:
Executable -Wl,-O1 -Wl,--as-needed
Module -Wl,-O1 -Wl,--as-needed
Shared -Wl,-O1 -Wl,--as-needed
-- Configuring incomplete, errors occurred!
|
I'd guess I need to turn off Python3_2 in dev-python/pyside-tools-0.2.14, or enable it in dev-python/pyside-1.1.2-r1, but I haven't had any luck doing either.
For good measure I have this set in my make.conf
| Code: |
#PYTHON_TARGETS="python2_7 python3_2"
#PYTHON_SINGLE_TARGET="python3_2"
|
and I have tried that uncommented and got worse build output;
| Code: |
Calculating dependencies... done!
The following packages are causing rebuilds:
(dev-python/sip-4.16.3::gentoo, ebuild scheduled for merge) causes rebuilds for:
(dev-python/PyQt4-4.11.1::gentoo, ebuild scheduled for merge)
(dev-python/qscintilla-python-2.7.2::gentoo, ebuild scheduled for merge)
[ebuild r U ~] dev-python/sip-4.16.3:0/11 [4.15.3:0/10] USE="doc -debug" PYTHON_TARGETS="python2_7 -python3_3* -python3_4% (-python3_2%)" 776 kB
[ebuild r U ~] dev-python/PyQt4-4.11.1 [4.10.3-r2] USE="X dbus declarative designer doc examples help kde multimedia opengl phonon script scripttools sql svg webkit xmlpatterns -debug" PYTHON_TARGETS="python2_7 -python3_3* -python3_4% (-python3_2%)" 10,859 kB
[ebuild R ] dev-python/pyside-1.1.2-r1 USE="X declarative help kde multimedia opengl phonon script scripttools sql svg webkit xmlpatterns {-test}" PYTHON_TARGETS="python2_7 (-python3_2)" 0 kB
[ebuild rR ] dev-python/qscintilla-python-2.7.2 USE="-debug" PYTHON_TARGETS="python2_7 (-python3_2) -python3_3*" 0 kB
[ebuild N ] dev-python/pyside-tools-0.2.14 USE="{-test}" 0 kB
|
I'm at a loss, mainly as I can't fathom how to unmask python3_2 without breaking everything - I'm assuming its masked as its in brackets. I haven't looked for why its masked but I assume its a good reason. I don't know why dev-python/pyside-tools-0.2.14 is ignoring python_targets, is this a bug? 
_________________
=== === === === === ===
doh
=== === === === === === |
|
| Back to top |
|
 |
charles17
Advocate
Joined: 02 Mar 2008
Posts: 3664
|
| Posted: Tue Sep 16, 2014 12:03 pm Post subject: Re: emerging dev-python/pyside-tools-0.2.14 |
|
|
Which python versions have you activated? Check | Quote: | | # eselect python list |
In case there were Python 3.2 *, then set Python 3.3 |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Tue Sep 16, 2014 3:16 pm Post subject: |
|
|
First of all, if those lines in make.conf start with '#', you didn't set a damn thing.
Second, pyside-tools still aren't migrated to python-r1, so only USE_PYTHON matters for it.
What you really want to do is either not use python3 in the whole pyside chain or reemerge the whole chain for python 3.3. |
|
| Back to top |
|
|
melts
n00b
Joined: 21 Feb 2004
Posts: 53
|
| Posted: Wed Sep 17, 2014 12:01 am Post subject: |
|
|
thanks voidmage, just so i know for future reference, how can i tell if something is migrated to python-r1?
I'm also a little stuck at how i could use python 3.3 when pyside_tools only seems to support 3.2 and 2.7. I'll attempt to merge it all as 2.7 using USE_PYTHON. If it then doesn't work as expected i'll re-visit it and see if i can get everything up to 3.3
and to clarify, the make.conf lines i posted were the setup i'm currently using, the code i copied after that with an emerge -va <packages> output is what happens when remove the hashes. I was commenting them out as setting them poorly like that make a mess of things.
_________________
=== === === === === ===
doh
=== === === === === === |
|
| Back to top |
|
|
VoidMage
Watchman
Joined: 14 Oct 2006
Posts: 6196
|
| Posted: Wed Sep 17, 2014 10:33 pm Post subject: |
|
|
Well, it's a mix of simple and complicated within this chain.
dev-python/pyside-tools-0.2.15 doesn't have restiction on python 3.3, but the real problem here is dev-python/shiboken - it uses a somewhat complicated macro to detect python, that has only a couple of python versions *hardcoded*.
The restrictions of the two later come from this reason alone, more than actual incompatibilities with more recent python versions (I'm not saying there aren't any, but this macro makes the maintainer reluctant in testing any more recent python versions). |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
