Summary: | dev-libs/boost-1.41.0-r3 build failure: long double support is not supported by Boost.Math on this Plaform | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcus Sen <msreg1> |
Component: | [OLD] Library | Assignee: | Dirkjan Ochtman (RETIRED) <djc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arne_bab, cpp+disabled, dev-zero, SebastianLuther |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcus Sen
2010-05-02 21:59:42 UTC
Built successfully after switching gcc from 4.1.2 to 4.3.4. (gcc-config switch then re-emerge libtool). Could a warning be added to boost, so it tells me when it fails that I might have to switch to gcc 4.3.x? (I found this bug through google after trying a few times to get boost to build) Currently I get this error: * ERROR: dev-libs/boost-1.41.0-r3 failed: * building boost failed * * Call stack: * ebuild.sh, line 54: Called src_compile * environment, line 5195: Called die * The specific snippet of code: * ${BJAM} ${NUMJOBS} -q -d+2 gentoorelease ${OPTIONS} threading=single,multi link=shared,static runtime-link=shared || die "building boost failed"; * * If you need support, post the output of 'emerge --info =dev-libs/boost-1.41.0-r3', * the complete build log and the output of 'emerge -pqv =dev-libs/boost-1.41.0-r3'. * The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.41.0-r3/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.41.0-r3/temp/environment'. * S: '/var/tmp/portage/dev-libs/boost-1.41.0-r3/work/boost_1_41_0' And this sadly doesn’t state at all what I need to do to make it build. And openoffice needs it. Both are marked stable, so I think there shouldn’t be build failures — at least not without clear information what went wrong and how to fix it. Is it possible to print a conditional error message? if current_gcc < 4.3.4: print "to build this package on your machine, you need to switch to a more recent version of gcc. See gcc-config." |