Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 557168 - dev-libs/boost-1.56.0-r1: failed to build on some ARM machines - error: ‘thread_fence’ is not a member of ‘boost::atomics::detail’
Summary: dev-libs/boost-1.56.0-r1: failed to build on some ARM machines - error: ‘thre...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: ARM Linux
: Normal normal (vote)
Assignee: C++ Team [disbanded]
URL:
Whiteboard:
Keywords: UPSTREAM
: 558042 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-08-09 17:43 UTC by Daniel Savard
Modified: 2015-08-25 11:36 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info '=dev-libs/boost-1.56.0-r1::gentoo' (boost.tar.bz2,36.42 KB, application/x-bzip)
2015-08-09 17:43 UTC, Daniel Savard 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Savard 2015-08-09 17:43:33 UTC 
Created attachment 408676 [details]
emerge --info '=dev-libs/boost-1.56.0-r1::gentoo'

I tried to build dev-libs/boost-1.56.0-r1 on my Raspberry Pi with and without distcc, locally or using compile servers, changing the number of available servers, inceasing the swap space and all these things failed.

I conclude boost has become impossible to build on the Raspberry Pi.

I opened a discussion here: https://forums.gentoo.org/viewtopic-p-7793848.html#7793848

The point where the build fails varies depending on the configuration of distcc, the number of cores available for remote compile or if it is compiled locally. Which ever method I used so far failed.

In the attached compressed tarfile, the result of the following commands and the following files:

emerge --info '=dev-libs/boost-1.56.0-r1::gentoo'
emerge -pqv '=dev-libs/boost-1.56.0-r1::gentoo'

/var/tmp/portage/dev-libs/boost-1.56.0-r1/temp/build.log
/var/tmp/portage/dev-libs/boost-1.56.0-r1/temp/environment
Comment 1 Jonas Stein gentoo-dev 2015-08-14 17:47:39 UTC 
Boost needs about 1 GB RAM per core during compile time, but you can optimize compile settings a bit. [1]

There were discussions on this topic on the Gentoo Workshop Troisdorf 2015 [2] too and the idea was to suggest a small change in the ebuild:

One could warn the user via einfo as done in 
sci-mathematics/polymake/polymake-2.14-r1.ebuild

I do not know if a test for sufficient RAM is trivial, because the compilation process may run under very different circumstances (distcc...)

So I want to suggest to add this warning (info) to the ebuild. 

===

[1] https://forums.gentoo.org/viewtopic-t-698458-start-0-postdays-0-postorder-asc-highlight-.html

[2] http://trolug.de/gentoo-workshop-troisdorf-2015.html (Compiler-Flags bei wenig RAM)
Comment 2 Sergey Popov gentoo-dev 2015-08-25 10:23:34 UTC 
*** Bug 558042 has been marked as a duplicate of this bug. ***
Comment 3 Sergey Popov gentoo-dev 2015-08-25 11:36:48 UTC 
commit 89f7694c5ab1f1860014549565ff919f87fb3f06
Author: Sergey Popov <pinkbyte@gentoo.org>
Date:   Tue Aug 25 14:35:41 2015 +0300

    dev-libs/boost: backport build fixes for Boost::Atomic
    
    Backport build fixes for atomic ops support on some ARM devices
    Upstream bugreport - https://svn.boost.org/trac/boost/ticket/10446
    
    Gentoo-Bug: 557168
    Reported-by: Daniel Savard <dsavard@cids.ca>
    Gentoo-Bug: 558042
    Reported-by: Michael Jones <gentoo@jonesmz.com>
    
    Package-Manager: portage-2.2.20