| View previous topic :: View next topic |
| Author |
Message |
Moriah
Advocate
Joined: 27 Mar 2004
Posts: 2365
Location: Kentucky
|
 Posted: Sat Jul 25, 2015 5:38 pm Post subject: HELP - USE_PYTHON='2.7' where? - SOLVED |
 |
|
Doing routine system weekly updates, I got:
| Code: |
* Messages for package sys-apps/kmod-20:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
|
"you need to set USE_PYTHON..."
Set it *WHERE* ???
This whole python update thing is bafflingly terse as to what a person needs to do. Since portage is written in python, I am cautious about messing with it, and the update directions seem to assume that one is a python developer, not a sysadm that just happens to need python to work for his systems to work.
Even the wiki page above is so terse as to be meaningless to the non-python person.
Yes, I write some python scripts, even some non-trivial ones, but I am not a seasoned python system maintainer, and the advice offered for the current upgrade assume that one is.
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword
Foghorn Leghorn is a Warner Bros. cartoon character.
Last edited by Moriah on Wed Jul 29, 2015 4:10 am; edited 1 time in total |
|
| Back to top |
|
 |
natrix
Guru
Joined: 23 Aug 2013
Posts: 556
|
| Posted: Sat Jul 25, 2015 10:28 pm Post subject: |
|
|
It say add this USEs to kmod:
| Code: | | python_targets_python2_7 python_single_target_python2_7 |
But, before, check it with "equery u sys-apps/kmod". This USEs is a default. |
|
| Back to top |
|
|
Moriah
Advocate
Joined: 27 Mar 2004
Posts: 2365
Location: Kentucky
|
| Posted: Sun Jul 26, 2015 4:12 am Post subject: |
|
|
OK, but where do I put this? It doesn't sound like the USE line in make.conf. It must be some kind of python configuration of something, or does it go in package.use?
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword
Foghorn Leghorn is a Warner Bros. cartoon character. |
|
| Back to top |
|
|
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Sun Jul 26, 2015 4:51 am Post subject: |
|
|
It goes in /etc/portage/make.conf next to the PYTHON_TARGETS variable which is the modern replacement for USE_PYTHON.
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
| Back to top |
|
|
Moriah
Advocate
Joined: 27 Mar 2004
Posts: 2365
Location: Kentucky
|
| Posted: Sun Jul 26, 2015 4:59 am Post subject: |
|
|
Since I don't have any PYTHON_TARGETS or USE_PYTHON in my make.conf, I take it this is on a line by itself, not on the USE line?
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword
Foghorn Leghorn is a Warner Bros. cartoon character. |
|
| Back to top |
|
|
while true
Guru
Joined: 07 Apr 2010
Posts: 532
Location: Ljubljana, Slovenia
|
| Posted: Sun Jul 26, 2015 7:36 am Post subject: |
|
|
oi, newbie here,
last night i eix-sync and it shower onlu mplayer is U.
| Code: | * Calling eix-diff
Diffing databases (18089 -> 18097 packages)
[<] == dev-ruby/jeweler (1.8.4 -> ~2.0.1-r2): Rake tasks for managing gems and versioning and a generator for creating a new project
[><] == dev-util/kdevelop-pg-qt (1.0.0-r2 -> 1.0.0-r2(4)): A LL(1) parser generator used mainly by KDevelop language plugins
[U] == media-video/mplayer (1.2_pre20150214@07/20/2015; 1.2_pre20150214^d -> 1.2_pre20150214-r1^d): Media Player for Linux
[>] == net-misc/tor (0.2.6.7 -> 0.2.6.10): Anonymizing overlay network for TCP
[><] == sys-kernel/gentoo-sources (4.0.5(4.0.5)@07/19/2015; 3.10.82(3.10.82)^bs 3.12.44(3.12.44)^bs 3.14.46(3.14.46)^bs 3.18.16(3.18.16)^bs 4.0.5(4.0.5)^bs -> 3.10.82(3.10.82)^bs 3.12.44(3.12.44)^bs 3.14.48(3.14.48)^bs 3.18.16(3.18.16)^bs 4.0.5(4.0.5)^bs): Full sources including the Gentoo patchset for the 4.1 kernel tree
[>] == www-plugins/chrome-binary-plugins (44.0.2403.89_p1(stable)^msd -> 44.0.2403.107_p1(stable)^msd): Binary plugins from Google Chrome for use in Chromium
[N] >> dev-lua/lanes (~3.10.0): lightweight, native, lazy evaluating multithreading library
[N] >> dev-perl/Devel-OverloadInfo (~0.2.0): Introspect overloaded operators
[N] >> dev-perl/Module-Install-AuthorTests (~0.2.0): Designate tests only run by module authors
[N] >> dev-perl/Module-Runtime-Conflicts (~0.2.0): Provide information on conflicts for Module::Runtime
[N] >> dev-perl/Test-CleanNamespaces (~0.180.0): Check for uncleaned imports
[N] >> media-libs/lvtk (~1.2.0): A set of C++ wrappers around the LV2 C API
[N] >> media-plugins/ams-lv2 (~1.1.0): A port of the AMS internal modules to LV2 plugins to create modular synthesizers
[N] >> media-plugins/calf (~0.0.60): A set of open source instruments and effects for digital audio workstations
* Time statistics: |
emerge --update --deep --newuse @world gave this:
| Code: | Calculating dependencies... done!
[ebuild R ] sys-apps/file-5.22 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-libs/boost-1.56.0-r1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] sys-apps/kmod-20 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild NS ] dev-lang/python-3.4.1 [2.7.9-r1, 3.3.5-r1] USE="gdbm ipv6 ncurses readline sqlite ssl threads xml -build -examples -hardened -tk -wininst"
[ebuild R ] dev-libs/libxml2-2.9.2-r1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] sys-apps/portage-2.2.20 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/setuptools-12.0.1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] x11-proto/xcb-proto-1.11 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/pillow-2.8.1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] app-portage/gentoolkit-0.3.0.9-r2 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/numpy-1.9.0-r1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/lxml-3.4.1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] virtual/python-imaging-2 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/dbus-python-1.2.0-r1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/pycairo-1.10.0-r4 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-python/pygobject-3.14.0 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] dev-libs/libpeas-1.12.1-r1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] app-editors/vim-7.4.273 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] sys-apps/util-linux-2.25.2-r2 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] app-editors/gedit-3.14.3 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] app-office/libreoffice-4.4.4.3 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild R ] app-editors/gedit-plugins-3.14.1 PYTHON_TARGETS="python3_4* -python3_3*"
[ebuild U ] media-video/mplayer-1.2_pre20150214-r1 [1.2_pre20150214]
Would you like to merge these packages? [Yes/No] |
i just woke up to this:
| Code: | * Messages for package dev-lang/python-3.4.1:
* You have just upgraded from an older version of Python.
*
* Please adjust PYTHON_TARGETS (if so desired), and run emerge with the --newuse or --changed-use option to rebuild packages installing python modules.
* Messages for package dev-libs/libxml2-2.9.2-r1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package sys-apps/portage-2.2.20:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-python/setuptools-12.0.1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package app-portage/gentoolkit-0.3.0.9-r2:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package x11-proto/xcb-proto-1.11:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-python/dbus-python-1.2.0-r1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package sys-apps/util-linux-2.25.2-r2:
* The mesg/wall/write tools have been disabled due to USE=-tty-helpers.
* Messages for package dev-python/pycairo-1.10.0-r4:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-python/pillow-2.8.1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-python/pygobject-3.14.0:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-libs/libpeas-1.12.1-r1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-python/lxml-3.4.1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package dev-python/numpy-1.9.0-r1:
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
* Messages for package app-office/libreoffice-4.4.4.3:
* If you plan to use lbase application you should enable java or you will get various crashes.
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date. |
i found this: https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS
but as newbie i am am not sure, is
PYTHON_TARGETS='2.7' or USE_PYTHON='2.7' supposed to go in, ehm, in /etc/portage/make.config?
and than emerge again and do that 'python-updater' to rebuild affected packages, or will that command rebuild stuff?
Thank you
_________________
Kind regards, Goran Mitic
alive
while true
kick ass |
|
| Back to top |
|
|
222697
n00b
Joined: 07 May 2010
Posts: 51
|
| Posted: Sun Jul 26, 2015 7:42 am Post subject: |
|
|
These package upgrade messages are also very poor for me. Took my time and searched in the forum, but still not sure what is that about and what is the impact.
I guess one shall add the line
USE_PYTHON='2.7'
to /etc/portage/make.conf
(have no USE_PYTHON setting currently in /etc/portage/make.conf)
and then run python-updater ?
But I am not really sure. Only legacy packages honour the USE_PYTHON variable in make.conf? No impact for modern packages?
Here my python version list
| Code: | # eselect python list
Available Python interpreters:
[1] python2.7
[2] python3.3 *
[3] python3.4 |
Doing the above guessed steps gives a disturbing error message:
| Code: | # python-updater
Traceback (most recent call last):
File "<string>", line 7, in <module>
ImportError: No module named 'portage'
* Starting Python Updater...
* Main active version of Python: 3.3
* Active version of Python 2: 2.7
* Active version of Python 3: 3.3
* Globally supported Python ABIs in installed repositories:
* No packages need to be reinstalled. |
|
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Sun Jul 26, 2015 8:31 am Post subject: |
|
|
| 1970 wrote: | | Only legacy packages honour the USE_PYTHON variable in make.conf? No impact for modern packages? |
Yes (for both). Unless you use ancient overlays, there is no need ot worry about USE_PYTHON. |
|
| Back to top |
|
|
Moriah
Advocate
Joined: 27 Mar 2004
Posts: 2365
Location: Kentucky
|
| Posted: Sun Jul 26, 2015 12:45 pm Post subject: |
|
|
So is that ditto for PYTHON_TARGETS as well? Just ignore the messages and carry on?
_________________
The MyWord KJV Bible tool is at http://www.elilabs.com/~myword
Foghorn Leghorn is a Warner Bros. cartoon character. |
|
| Back to top |
|
|
while true
Guru
Joined: 07 Apr 2010
Posts: 532
Location: Ljubljana, Slovenia
|
| Posted: Sun Jul 26, 2015 12:52 pm Post subject: |
|
|
so, for noobs like me, put both in make.config?
USE_PYTHON='2.7'
and
PYTHON_TARGETS='2.7'
thank you
_________________
Kind regards, Goran Mitic
alive
while true
kick ass |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Sun Jul 26, 2015 1:41 pm Post subject: |
|
|
| Moriah wrote: | | So is that ditto for PYTHON_TARGETS as well? |
It depends what you wnat.
PYTHON_TARGETS and PYTHON_SINGLE_TARGET are used by current packages. They are used to decide for/with which python versions the package is installed.
If you do not set them in /etc/portage/make.conf, then "safe" defaults are set for these variables. Currently, this means that all python packages are build for python-2.7 as well as for python-3.4 (if the packages can be built for these). Later on, this defaults may change.
Since very likely you do not need all python packages for python-2.7 and python-3.4, you can strip down your system here and set packages individually. However, this is a lot of work.
Summarizing: If you want it simple, do not set these variables, and rely that the developes choose sane defaults for them (which they do).
You observed just a big recompilation, because these defaults were just changed (from python-3.3 ot python 3.4). If you want to fine-tune your system and strip down unneeded libraries, you can select only one python-3.4 for most packages and python-2.7 for those which need it. Perhaps you can even get rid of one of the python versoins at all. As usual, such fine-tuning can be rather cumbersome. |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Sun Jul 26, 2015 1:42 pm Post subject: |
|
|
| while true wrote: | so, for noobs like me, put both in make.config?
USE_PYTHON='2.7'
and
PYTHON_TARGETS='2.7' |
No, better put no such variables in make.conf (unless you use package no longer in the gentoo tree). |
|
| Back to top |
|
|
while true
Guru
Joined: 07 Apr 2010
Posts: 532
Location: Ljubljana, Slovenia
|
| Posted: Sun Jul 26, 2015 3:05 pm Post subject: |
|
|
hey mv,
so what should i do now?
| Code: | keeshta grom # eselect python list
Available Python interpreters:
[1] python2.7 *
[2] python3.3
[3] python3.4 |
just run python-updater or ignore the whole thing?
thank you
_________________
Kind regards, Goran Mitic
alive
while true
kick ass |
|
| Back to top |
|
|
mv
Watchman
Joined: 20 Apr 2005
Posts: 6747
|
| Posted: Sun Jul 26, 2015 3:27 pm Post subject: |
|
|
| while true wrote: | | just run python-updater or ignore the whole thing? |
Actually, even python-updater shouldn't have to do anything after a regular update.
Unrelated, but probably it is meanwhile safe to switch to python-3.4 as the system's python. This might give you a slight speed increase in e.g. portage. |
|
| Back to top |
|
|
natrix
Guru
Joined: 23 Aug 2013
Posts: 556
|
| Posted: Sun Jul 26, 2015 4:34 pm Post subject: |
|
|
Only add the next line in the file "package.use", with it you are safe:
| Code: | | sys-apps/kmod python_targets_python2_7 python_single_target_python2_7 |
|
|
| Back to top |
|
|
jburns
Veteran
Joined: 18 Jan 2007
Posts: 1214
Location: Massachusetts USA
|
| Posted: Sun Jul 26, 2015 4:44 pm Post subject: |
|
|
python3.4 hould be selected as the active Python 3 interpreter. | Code: | | eselect python update --python3 |
For the one package that I checked that had the USE_PYTHON='2.7' message, the python2.7 files were being generated.[/code][/list] |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2963
Location: Edge of marsh USA
|
| Posted: Sun Jul 26, 2015 6:48 pm Post subject: |
|
|
NEVER MIND WHAT I WROTE BELOW: I've had Python 3 masked for several years to avoid the nuisance.
If I add Python 3.4 to /etc/make.conf (according to the news message), or if I remove the PYTHON lines from make.conf, the message I get is that it is masked.
What is an ordinary user supposed to do? I still feel fairly clueless. As a long-time user, this is not good.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2963
Location: Edge of marsh USA
|
| Posted: Sun Jul 26, 2015 7:10 pm Post subject: |
|
|
I think this is going to work. The update is currently running on my desktop system.
I removed the PYTHON entries from make.conf, unmasked my set mask for Python 3 in /etc/portage/package.mask, and am now running:
emerge -uDN world which is compiling 42 ebuilds.
It doesn't look like I'll need to do anything else except set Python 3.4 as the default using eselect once the update has finished running.
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
as.gentoo
Guru
Joined: 07 Aug 2004
Posts: 319
|
| Posted: Sun Jul 26, 2015 11:06 pm Post subject: |
|
|
Is the following a mistake?
[ebuild R ] dev-python/sip-4.16.9:0/11::gentoo USE="-debug -doc" PYTHON_TARGETS="python2_7 -python3_3* python3_4*" 0 KiB
| Quote: | * Messages for package dev-python/sip-4.16.9:
* Package: dev-python/sip-4.16.9
* Repository: gentoo
* Maintainer: qt@gentoo.org
* Upstream: phil@riverbankcomputing.com pyqt@riverbankcomputing.com
* USE: abi_x86_64 amd64 elibc_glibc kernel_linux
python_targets_python2_7 python_targets_python3_4 userland_GNU
* FEATURES: preserve-libs sandbox splitdebug userpriv usersandbox
* Applying sip-4.15.5-darwin.patch ...
* It seems that you need to set USE_PYTHON to make sure that legacy
* packages will be built with respect to PYTHON_TARGETS correctly:
*
* USE_PYTHON='2.7'
*
* Please note that after changing the USE_PYTHON variable, you may need
* to run 'python-updater' to rebuild affected packages.
*
* For more information on PYTHON_TARGETS and python.eclass
* compatibility, please see the relevant Wiki article [1].
*
* [1] https://wiki.gentoo.org/wiki/Project:Python/PYTHON_TARGETS |
the website reads
| Quote: | [...]
python.eclass packages
The remaining packages (that can be identified by not having PYTHON_TARGETS USE flags) work in a different way.
If the user does not specify USE_PYTHON in make.conf (the default case), the packages are built for the versions of Python 2 and Python 3 which are installed and selected via eselect python.
Alternatively, the user may specify the requested implementations in USE_PYTHON. The possible values are listed in the USE_PYTHON column of the implementations list. |
So the second half of the text ("If the user does...") is irrelevant because dev-python/sip does have PYTHON_TARGETS set? |
|
| Back to top |
|
|
figueroa
Advocate
Joined: 14 Aug 2005
Posts: 2963
Location: Edge of marsh USA
|
| Posted: Mon Jul 27, 2015 2:25 am Post subject: |
|
|
Best I can tell, wtih "emerge -uDN world" everything got rebuilt for both Python 2.7 and 3.4 with NOTHING in the configuration files. Doing nothing to set a particular Python seems like a reasonable option.dev-python:pygame-1.9.2_pre20120101-r2:20150726-194739.log
_________________
Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
| Back to top |
|
|
Fitzcarraldo
Advocate
Joined: 30 Aug 2008
Posts: 2034
Location: United Kingdom
|
| Posted: Mon Jul 27, 2015 1:38 pm Post subject: |
|
|
I did not need to add any PYTHON-related environment variable assignments to /etc/portage/make.conf.
Firstly, the following command ran to completion without any error messages:
However, when I then used the following command it complained about Python (I cannot remember the precise error message):
| Code: | | emerge --ask --depclean |
and told me to use the following command:
| Code: | | emerge --update --newuse --deep --with-bdeps=y @world |
which I did. It rebuilt a few packages and all is fine again.
I still don't have any PYTHON environment variables in /etc/portage/make.conf:
| Code: | # grep PYTHON /etc/portage/make.conf
# |
_________________
Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC udev elogind & KDE on both.
Fitzcarraldo's blog |
|
| Back to top |
|
|
|
Portage & Programming
