Thelma
On 01/29/2017 01:56 PM, the...@sys-concept.com wrote: > I haven't updated my system for over a year (1year and 3-months). [snip] I got stuck on: dev-libs/boost-1.62.0-r1 i686-pc-linux-gnu-g++: error: unrecognized command line option ‘-std=c++14’ ...failed updating 1 target... * ERROR: dev-libs/boost-1.62.0-r1::gentoo failed (compile phase): * Building of Boost libraries failed * * Call stack: * ebuild.sh, line 115: Called src_compile * environment, line 4366: Called multilib-minimal_src_compile * environment, line 2481: Called multilib_foreach_abi 'multilib-minimal_abi_src_compile' * environment, line 2712: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 2359: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile' * environment, line 2357: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile' * environment, line 413: Called multilib-minimal_abi_src_compile * environment, line 2475: Called multilib_src_compile * environment, line 2968: Called building * environment, line 2936: Called die * The specific snippet of code: * ejam "${OPTIONS[@]}" ${PYTHON_OPTIONS} || die "Building of Boost libraries failed"; * * If you need support, post the output of `emerge --info '=dev-libs/boost-1.62.0-r1::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.62.0-r1::gentoo'`. * The complete build log is located at '/var/log/portage/dev-libs:boost-1.62.0-r1:20170131-012931.log'. * For convenience, a symlink to the build log is located at '/var/tmp/portage/dev-libs/boost-1.62.0-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.62.0-r1/temp/environment'. * Working directory: '/var/tmp/portage/dev-libs/boost-1.62.0-r1/work/boost_1_62_0-abi_x86_32.x86' * S: '/var/tmp/portage/dev-libs/boost-1.62.0-r1/work/boost_1_62_0' >>> Failed to emerge dev-libs/boost-1.62.0-r1, Log file: Is there a work around this error? -- Thelma