I'd like to help with bug #2713: I'm big fan of VAAPI and I want it back on Sabayon, but some tests are needed. Since I have Intel/nVidia/AMD graphic cards available, I want to do some tests. However, when I try to
- Code: Select all
USE="vaapi" emerge vlc xbmc
- Code: Select all
>>> Jobs: 0 of 4 complete, 1 failed Load avg: 1.27, 1.19, 0.88
* Package: dev-util/boost-build-1.39.0
* Repository: gentoo
* Maintainer: dev-zero@gentoo.org SebastianLuther@gmx.de,hwoarang@gentoo.org,cpp@gentoo.org
* USE: amd64 elibc_glibc kernel_linux multilib userland_GNU
* FEATURES: preserve-libs sandbox splitdebug
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/dev-util/boost-build-1.39.0/work
>>> Preparing source in /var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools ...
* Applying boost-build-1.42-env-whitespace.patch ...
[ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools ...
###
### Using 'cc' toolset.
###
rm -rf bootstrap
mkdir bootstrap
x86_64-pc-linux-gnu-gcc -o bootstrap/mkjambase0 -Wl,-O1,--as-needed mkjambase.c
x86_64-pc-linux-gnu-gcc: error trying to exec 'as': execvp: Too many levels of symbolic links
* ERROR: dev-util/boost-build-1.39.0 failed (compile phase):
* building bjam failed
*
* Call stack:
* ebuild.sh, line 84: Called src_compile
* environment, line 2783: Called die
* The specific snippet of code:
* LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed";
*
* If you need support, post the output of 'emerge --info =dev-util/boost-build-1.39.0',
* the complete build log and the output of 'emerge -pqv =dev-util/boost-build-1.39.0'.
* The complete build log is located at '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/environment'.
* S: '/var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools'
* Messages for package dev-util/boost-build-1.39.0:
* ERROR: dev-util/boost-build-1.39.0 failed (compile phase):
* building bjam failed
*
* Call stack:
* ebuild.sh, line 84: Called src_compile
* environment, line 2783: Called die
* The specific snippet of code:
* LIBS=${LDFLAGS} CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed";
*
* If you need support, post the output of 'emerge --info =dev-util/boost-build-1.39.0',
* the complete build log and the output of 'emerge -pqv =dev-util/boost-build-1.39.0'.
* The complete build log is located at '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/boost-build-1.39.0/temp/environment'.
* S: '/var/tmp/portage/dev-util/boost-build-1.39.0/work/boost_1_39_0/tools'
