First, it should be noted that dev-util/boost-build-1.53.0 fails to build on this arch/profile but there is a "fix" bug #496446. ("Fix" is in quotes because the solution suggested there probably breaks other things.) Nonetheless, adopting that fix, boost-1.53.0-r1 fails to build ending in some python/multilib error which I can't quite make out. Please note that default/linux/mips/13.0/mipsel/multilib/n32 supports 3 abis: o32 in /lib or /usr/lib n32 in /lib32 or /usr/lib32 n64 in /lib64 or /usr/lib64 This was not a problem with boost-1.49.0-r2. Reproducible: Always
cc-ing the python team since they might have a clue. I should emphasis that it builds with USE=-python.
Can you provide a build log from after your "fix" from 496446?
Created attachment 367234 [details] Failed build on mip64el multilib o32/n32/n64 with USE=python This is trying to upgrade as follows: [ebuild U ] dev-libs/boost-1.53.0-r1 [1.49.0-r2] USE="nls%* python threads%* -debug -doc -icu (-mpi) -static-libs -tools" PYTHON_TARGETS="python2_7%* python3_2%* -python2_6% -python3_3%"
Created attachment 377640 [details] Failed build on mip64el multilib o32/n32/n64 with USE=python Previous attachment was double gzipped.
(In reply to Matt Turner from comment #4) > Created attachment 377640 [details] > Failed build on mip64el multilib o32/n32/n64 with USE=python > > Previous attachment was double gzipped. It's bug in bugzilla and/or web browsers. Reattaching won't help :P.
Probably bug #496446 fixes that one as well, please check