| Summary: | dev-libs/boost-1.52.0-r5 - .../temp/environment: line 964: 31328 Segmentation fault b2 "$@" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ryuichi KAWAMATA <iam> |
| Component: | [OLD] Library | Assignee: | C++ Team [disbanded] <cpp+disabled> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | gottlieb |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ryuichi KAWAMATA
2012-12-19 01:36:02 UTC
I am pretty sure this has nothing to do with sys-devel/gcc. Confirmed here ~amd64. (In reply to Allan Gottlieb from comment #2) > Confirmed here ~amd64. And again (~amd64) with boost-1-52.0-r6. Looks to be same problem. build.log ends with >>> Source prepared. >>> Configuring source in /mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/work/boost_1_52_0 ... >>> Source configured. >>> Compiling source in /mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/work/boost_1_52_0 ... b2 gentoorelease -j999 -q -d+2 --user-config=/mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/work/boost_1_52_0/user-config.jam --disable-icu boost.locale.icu=off --without-mpi --without-python pch=off --boost-build=/usr/share/boost-build --prefix="/mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/image/usr" --layout=system threading=multi link=shared --without-context Building the Boost C++ Libraries. /mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/temp/environment: line 1093: 9362 Aborted b2 "$@" * ERROR: dev-libs/boost-1.52.0-r6::gentoo failed (compile phase): * Building of Boost libraries failed * * Call stack: * ebuild.sh, line 93: Called src_compile * environment, line 3721: Called building * environment, line 3689: Called die * The specific snippet of code: * ejam ${OPTIONS} $(use python && echo --python-buildid=${EPYTHON#python}) || die "Building of Boost libraries failed"; * * If you need support, post the output of `emerge --info '=dev-libs/boost-1.52.0-r6::gentoo'`, * the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.52.0-r6::gentoo'`. * The complete build log is located at '/mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/temp/build.log'. * The ebuild environment file is located at '/mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/temp/environment'. * Working directory: '/mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/work/boost_1_52_0' * S: '/mnt/h/portage-tmpdir/portage/dev-libs/boost-1.52.0-r6/work/boost_1_52_0' Hi, try to modify the MAKEOPTS variable in /etc/portage/make.conf or set it temporarly to something like "-j 4". I had exactly the same error with dev-libs/boost-1.52.0-r6 and was wondering about the -j999 in the b2 command. Using a value smaller 50 worked on my system. Best Regards, donnerzusel (In reply to Thomas from comment #4) > try to modify the MAKEOPTS variable in /etc/portage/make.conf or set it > temporarly to something like "-j 4". Bingo. I had failures on two amd64 systems. I tried one with --jobs 4 and one with --jobs 1. Both worked! I now set /etc/portage/package.env to use --jobs 4 with boost. thanks, allan *** This bug has been marked as a duplicate of bug 498134 *** |
