dev-libs/boost-1.55.0-r1 is failing when emerge with default PYTHON_TARGETS and USE flags. I tried with different python targets and switched of all USE flags, same result always. Reproducible: Always Steps to Reproduce: 1. emerge =dev-libs/boost-1.55.0-r1 2. 3. Actual Results: failing, see attachement for more info. Expected Results: success compile and install
Created attachment 373732 [details] gentoo-bug-dev-libs-boost-1.55.0-r1-build-log build log
Created attachment 373734 [details] emerge --info portage environment report
* dependency graph for dev-libs/boost-1.55.0-r1 `-- dev-libs/boost-1.55.0-r1 ~amd64 `-- dev-libs/icu-52.1 (>=dev-libs/icu-3.6) ~amd64 `-- virtual/libiconv-0-r1 (virtual/libiconv) ~amd64 `-- sys-cluster/openmpi-1.6.5 (sys-cluster/openmpi) ~amd64 [cxx] `-- sys-cluster/mpich2-1.5 (sys-cluster/mpich2) amd64 [cxx threads] `-- dev-lang/python-2.6.9 (>=dev-lang/python-2.6.8-r3) ~amd64 `-- dev-lang/python-2.7.6 (>=dev-lang/python-2.7.5-r2) ~amd64 `-- dev-lang/python-3.2.5-r3 (>=dev-lang/python-3.2.5-r2) amd64 `-- dev-lang/python-3.3.4 (>=dev-lang/python-3.3.2-r2) ~amd64 `-- dev-lang/python-exec-2.0.1-r1 (dev-lang/python-exec) amd64 [python_targets_python2_6(-)? python_targets_python2_7(-)? python_targets_python3_2(-)? python_targets_python3_3(-)? -python_single_target_python2_6(-) -python_single_target_python2_7(-) -python_single_target_python3_2(-) -python_single_target_python3_3(-)] `-- app-arch/bzip2-1.0.6-r7 (app-arch/bzip2) ~amd64 `-- sys-libs/zlib-1.2.8-r1 (sys-libs/zlib) amd64 `-- dev-util/boost-build-1.55.0 (=dev-util/boost-build-1.55*) ~amd64 `-- sys-apps/coreutils-8.22 (>=sys-apps/coreutils-8.5) ~amd64 [ dev-libs/boost-1.55.0-r1 stats: packages (14), max depth (1) ]
I don't understand exactly the issue here, but I tried to mask that 1.55 build in /etc/portage/package.mask, in other way I tried to emerge last working package, but the dev-libs/boost-1.54.0-r1 is failing in the same way. On the other hand the dev-util/boost-build-1.53.0 is working just fine
One update, this package is marked as unstable, I found that month ago I reconfigure my host to work with ACCEPT_KEYWORDS="~amd64", so the latest stable is working of course :-)) anyway from 3 versions available only the first one is compilable. Here is current keyword table: Keywords for dev-libs/boost: | | u | | a a a p s | n | | l m r h i m m p s p | u s | r | p d a m p a 6 i p c 3 a x | s l | e | h 6 r 6 p 6 8 p p 6 9 s r 8 | e o | p | a 4 m 4 a 4 k s c 4 0 h c 6 | d t | o -------------+-----------------------------+------------+------- [M]1.49.0-r2 | + + + o + + o ~ + + + + + + | o 0 | gentoo -------------+-----------------------------+------------+------- 1.52.0-r6 | + + + o + + o ~ + + ~ ~ + + | o 0/1.52 | gentoo -------------+-----------------------------+------------+------- [I]1.53.0-r1 | ~ ~ ~ o ~ ~ o ~ ~ ~ ~ ~ ~ ~ | o 0/1.53 | gentoo - compilable -------------+-----------------------------+------------+------- 1.54.0-r1 | ~ ~ ~ o ~ ~ o ~ ~ ~ ~ ~ ~ ~ | o 0/1.54 | gentoo - this bug -------------+-----------------------------+------------+------- 1.55.0-r1 | ~ ~ ~ o ~ ~ o ~ ~ ~ ~ ~ ~ ~ | o 0/1.55.0 | gentoo - this bug
forum link: http://forums.gentoo.org/viewtopic-p-7525434.html#7525434
It is not wrong value, I calculate -j flag as: n_of_cpu_threads*2 + 1, on my 64 opteron core system it is 65. In my /etc/portage/make.conf I have: CFLAGS=" -march=bdver1 -mtune=bdver1 -O2 -pipe -ggdb -frecord-gcc-switches -mprefer-avx128 -mieee-fp" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j65" And it is utilizing all cores when emerging if possible. If I do the same with for example manual compilation, then make with -j 65 also works without any issue. My system: 3.13.7-gentoo portage-2.2.10
the described bug is not related to -j 65 value in any way - I think :-)
Yes it is, check your error output? Set MAKEOPTS to "-j64" and see if that works for you. In any case, this is an upstream bug.
+ 07 Apr 2014; Sergey Popov <pinkbyte@gentoo.org> boost-1.53.0-r1.ebuild, + boost-1.54.0-r1.ebuild, boost-1.55.0-r1.ebuild: + Fix parallel compilation with high number of MAKEOPTS jobs, wrt bugs #506064 + and #498134 Thanks for the report. Fixed now.
