Lieber Besucher, herzlich willkommen bei: GentooForum.de. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
Zitat
# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-O2 -pipe"
CXXFLAGS="${CFLAGS}"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="bindist mmx sse sse2"
PORTDIR="/usr/portage"
DISTDIR="${PORTDIR}/distfiles"
PKGDIR="${PORTDIR}/packages"
GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/ ftp://mirror.switch.ch/mirror/gentoo/"
MAKEOPTS="-j4"
EMERGE_DEFAULT_OPTS="--jobs=2 --load-average=12 --ask --verbose"
VIDEO_CARDS="nvidia"
ACCEPT_LICENSE="*"
INPUT_DEVICES="evdev"
PYTHON_TARGETS="python2_7 python3_4 pypy1_9 jython2_5"
#Some Desktopconfig USE-Flags
USE="${USE} X kde qt4 gtk alsa python cdrdao opengl -gnome"
#Additional Steam Runtime USE-Flag
USE="${USE} steam-runtime"
#Additional USE-Flag for Intel SandyBridge and obove Optimizations
USE="${USE} sna"
#USE Flags for WINE IS NOT AN EMULATOR
USE="${USE} fontconfig gecko jpeg lcms mp3 png truetype pulseaudio realtime nls udisks xcomposite ncurses ssl abi_x86_32 abi_x86_64 perl run-exes staging threads xml"
#Jackserver USE-Flag
USE="${USE} jack"
#Using FFMPEG instead of LIBAV
USE="${USE} ffmpeg -libav"
#The End of /etc/portage/make.conf reserved for layman!
source /var/lib/layman/make.conf
Zitat
Title PYTHON_TARGETS deployment
Author MichaŠGórny <mgorny@gentoo.org>
Posted 2012-11-06
Revision 1
Recently, a few new Python eclasses have been deployed. As ebuilds
migrate, the way they support multiple Python implementations will
change. The previous method built Python modules for Python
implementations selected through `eselect python'. The new method uses
the PYTHON_TARGETS USE flags to explicitly name the implementations the
modules shall be built for.
If you are running a modern system with only Python 2.7 & 3.2 installed,
then you don't have to do anything. The defaults will simply fit you,
and let you keep your system up-to-date when new Python versions are
deployed.
However, if you'd like to use another set of Python implementations, you
will need to set PYTHON_TARGETS in your make.conf file appropriately.
This variable names the enabled implementations in the standard way
common to all USE_EXPAND variables.
For example, a setup enabling all major Python implementations would
look like:
PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5"
The variable should list all Python implementations which are going to
be used on the system; missing a particular value there will result
in missing Python modules.
A complete list of all possible values can be obtained using a command
equivalent to the following:
emerge -1pv dev-python/python-exec
For more details, please see the python-r1 User's Guide [1].
[1] http://www.gentoo.org/proj/en/Python/pyt…/user-guide.xml
Zitat
For example, a setup enabling all major Python implementations would
look like:
PYTHON_TARGETS="python2_7 python3_2 pypy1_9 jython2_5"
Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von »solarseed« (29.07.2015, 11:28)