See build log attachment
Steps to Reproduce:
1. install python2 and python3
2. emerge lv2core
Failed to emerge
It seems to me that problem is in python version
When I manually replace
#! /usr/bin/env python
#! /usr/bin/env python2
in "/var/tmp/portage/media-libs/lv2core-3.0/work/lv2core-3.0/waf" file, "./waf configure" goes fine
Created attachment 310665 [details]
Created attachment 310667 [details]
The wscript should explicitly request python 2 . requesting just "python" uses whatever eselect python has. Eselecting python2 also works.
If this is still current (not yet fixed) you can try this:
before inherit, add:
to the "inherit"-line and add:
just before the src_prepare() or src_configure()-functions
Created attachment 394908 [details, diff]
patch to fix lv2core-3.0 ebuild on systems with python 3.
This patch fixes the ebuild so that this package can be emerged on systems where python2 is not the system default interpreter.
The year is 2015 and this bug still exists... I have added a patch to the ebuild to fix it, please take a look at it.
Created attachment 395178 [details]
ebuild for lv2core-3.0 rewritten for EAPI=4 and current python class
The ebuild for stable lv2core-3.0 is out of date with current standards and does not emerge on systems where python 3 is the default interpreter. This attachment is a new ebuild uses the current python eclass and will install correctly regardless of the default python interpreter.
happened at stable too:
This is an stable amd64 chroot image (named amd64-13.0-stable_20150802-112257) at a hardened host acting as a tinderbox.
Portage 2.2.20 (python 3.4.1-final-0, default/linux/amd64/13.0, gcc-4.8.4, glibc-2.20-r2, 4.0.8-hardened x86_64)
System uname: Linux-4.0.8-hardened-x86_64-Intel-R-_Core-TM-_i7-3770_CPU_@_3.40GHz-with-gentoo-2.2
KiB Mem: 16164692 total, 1409720 free
Probably time to stabilize a newer version using current python eclasses
x86 stable. Closing.