Im having issues compiling cryptocoin programs that rely on Boost. They contain a file inside their builds "depends/packages/boost.mk" that uses /usr/share/boost-build/site-config.jam on our gentoo systems. This file contains the command b2 which is used to build boost in our local builds. However it causes the builds to fail unless the file is edited to have --ignore-site-config added to the b2 line(s). The only solutions I have found is to manually edit each builds boost.mk file and add that option or to edit site-config.jam.. the latter being the better choice. Im just not sure what to add to site-config.jam to get b2 to automatically use the --ignore-site-config option. So is there a way to fix this upstream in the ebuilds or can someone chime in and inform us what to add to /etc/site-config.jam so we dont have to keep on editing github builds that rely on boost. As seen here in bug ID# 456792 (https://bugs.gentoo.org/456792) its unclear how to edit that file. Other gentoo users having the same issue who had to manually edit their builds. https://github.com/zcash/zcash/issues/1654 https://github.com/ruslo/hunter/issues/423 https://stackoverflow.com/questions/23013433/how-to-install-modular-boost https://github.com/ethereum/cpp-ethereum/issues/4206
further reading.. the only viable solution is to comment out the two lines in site-config.jam when doing builds and then removing the comments after the build is complete. Is there a more elegant work-around?
Please provide a patch or an example site-config.jam file.
Created attachment 679790 [details] Example site-config.jam Hey, got hit with issue as well. Regarding the file, id propose to remove the none options one way or another. As these are options that cant be parsed. Changes and the reasoning for some: Release variant optimization flag set to speed, but space could be more desirable for some. Release variant debug-symbols flag is set to off. Debug variant optimization flag set to off. The optimization and debug-symbols flags could also be completely omitted as well, and instead let the specific build configurations set it themselves rather than override them.
