"Building database (/var/cache/eix/portage.eix) ..
[0] 'gentoo' /usr/portage/ (cache: metadata-md5-or-flat)
Reading category 163|163 (100%) Finished
[1] 'sabayon-distro' /var/lib/layman/sabayon-distro (cache: parse|ebuild*#metadata-md5#metadata-assign#assign)
Reading category 136|163 ( 83%): sys-devel .. * ERROR: sys-devel/base-gcc-4.7.3::sabayon-distro failed (depend phase):
* Need to upgrade to at least EAPI=2
*
* Call stack:
* ebuild.sh, line 550: Called source '/var/lib/layman/sabayon-distro/sys-devel/base-gcc/base-gcc-4.7.3.ebuild'
* base-gcc-4.7.3.ebuild, line 21: Called inherit 'eutils' 'toolchain'
* ebuild.sh, line 280: Called __qa_source '/usr/portage/eclass/toolchain.eclass'
* ebuild.sh, line 80: Called source '/usr/portage/eclass/toolchain.eclass'
* toolchain.eclass, line 29: Called die
* The specific snippet of code:
* 0|1) die "Need to upgrade to at least EAPI=2";;
*
* If you need support, post the output of `emerge --info '=sys-devel/base-gcc-4.7.3::sabayon-distro'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/base-gcc-4.7.3::sabayon-distro'`.
* Working directory: '/usr/lib64/python2.7/site-packages'
* S: '/base-gcc-4.7.3'
ebuild failed with status 1
Reading category 136|163 ( 83%): sys-devel ..
Could not properly execute /var/lib/layman/sabayon-distro/sys-devel/base-gcc/base-gcc-4.7.3.ebuild
Reading category 163|163 (100%) Finished"
This is the error, only for information :D
The upstream toolchain eclass is restricting the 'go' USE
flag to >=gcc-4.7.x.
The change synchronizes sys-devel/gcc-4.6.3 with the Sabayon
version of sys-devel/base-gcc-4.6.3 which also required
changes around the implementation of the 'go' USE flag.
Signed-off-by: Mitch Harder <mitch.harder@sabayonlinux.org>
The upstream toolchain eclass has changed so that the 'go'
USE flag is no longer in IUSE for <gcc-4.7.
Portage throws out an error now if flags are not in IUSE.
The only place that the 'go' USE flag is implemented in this
ebuild is for a PDEPEND on sys-devel/gcc-config, however,
the upstream toolchain eclass alredy has a higher dependency,
and we already have the appropriate sys-devel/gcc-config
in Entropy.
So I just removed the PDEPEND line, deferring to the PDEPEND
in the toolchain eclass.
Signed-off-by: Mitch Harder <mitch.harder@sabayonlinux.org>
When implementing a check for a valid gcc profile to build the
split Sabayon gcc packages, I wanted to place that check into
the package_pretend() phase, which required an EAPI change.
I later discovered that the toolchain eclass is not structured to
fully support higher EAPI's, but I did not fully revert my changes.
Provide version 4.6.3 ebuilds for Sabayon's split gcc package,
sys-devel/base-gcc-4.6.3 and sys-devel/gcc/gcc-4.6.3.ebuild.
These ebuilds contain checks to make sure a different slotted gcc
is the active profile. Breakage can occur if you try to upgrade
with a gcc profile from the same slot as the upgrade version
when upgrading the Sabayon split packages.
our sys-devel/gcc stopped installing libffi, no further investigation
has been done since more and more packages require libffi.
So move it back to base-gcc.
Recent changes in portage have started throwing exceptions with
the way IUSE was implemented in Sabayon's split GCC ebuilds.
This change updates IUSE to be compatible with these changes.
Heather
mudler
Lox
Joost Ruis
Fabio Erculiani
BlackNoxis
Mitch Harder