Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] ebuild dev-libs/boost-1.56.0-r1 on Rasp Pi failed
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
AchilleTalon
Guru
Guru


Joined: 11 Apr 2004
Posts: 349
Location: Montreal, Quebec, Canada

PostPosted: Thu Aug 06, 2015 12:11 pm    Post subject: [SOLVED] ebuild dev-libs/boost-1.56.0-r1 on Rasp Pi failed Reply with quote

I failed compiling dev-libs/boost-1.56.0-r1 on Raspberry Pi. I was cross-compiling using distcc taking advantage of a more powerful machine. So, I reduced the number of parallel compile threads without success and I finally tried to compile locally as I had to do with gcc 4.8.4 without any success neither.

Here is the compile process log, there is no obvious error, at least for me.

Code:
>>> Compiling source in /var/tmp/portage/dev-libs/boost-1.56.0-r1/work/boost_1_56_0 ...
 * .arm: running multilib-minimal_abi_src_compile
 * python3_4: running building
b2 --user-config=/var/tmp/portage/dev-libs/boost-1.56.0-r1/work/boost_1_56_0-.arm/user-config.jam gentoorelease -j2 -q -d+2 --disable-icu boost.locale.icu=off --without-mpi --without-context --without-coroutine pch=off --boost-build=/usr/share/boost-build --prefix="/var/tmp/portage/dev-libs/boost-1.56.0-r1/image/usr" --layout=system threading=multi link=shared --python-buildid=3.4
Performing configuration checks

    - has_icu builds           : no
warning: Graph library does not contain MPI-based parallel components.
note: to enable them, add "using mpi ;" to your user-config.jam
    - zlib                     : yes
    - x86                      : no
    - arm                      : yes
    - lockfree boost::atomic_flag : no
    - gcc visibility           : yes
    - long double support      : yes

Building the Boost C++ Libraries.


    - iconv (libc)             : yes

Component configuration:

    - atomic                   : building
    - chrono                   : building
    - container                : building
    - context                  : not building
    - coroutine                : not building
    - date_time                : building
    - exception                : building
    - filesystem               : building
    - graph                    : building
    - graph_parallel           : building
    - iostreams                : building
    - locale                   : building
    - log                      : building
    - math                     : building
    - mpi                      : not building
    - program_options          : building
    - python                   : building
    - random                   : building
    - regex                    : building
    - serialization            : building
    - signals                  : building
    - system                   : building
    - test                     : building
    - thread                   : building
    - timer                    : building
    - wave                     : building

common.mkdir bin.v2/libs/atomic

        mkdir -p "bin.v2/libs/atomic"
   
common.mkdir bin.v2/libs/system/build/gcc-4.8/gentoorelease

        mkdir -p "bin.v2/libs/system/build/gcc-4.8/gentoorelease"
   
common.mkdir bin.v2/libs/atomic/build

        mkdir -p "bin.v2/libs/atomic/build"
   
common.mkdir bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off

        mkdir -p "bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off"
   
common.mkdir bin.v2/libs/atomic/build/gcc-4.8

        mkdir -p "bin.v2/libs/atomic/build/gcc-4.8"
   
common.mkdir bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off

        mkdir -p "bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off"
   
common.mkdir bin.v2/libs/atomic/build/gcc-4.8/gentoorelease

        mkdir -p "bin.v2/libs/atomic/build/gcc-4.8/gentoorelease"
   
common.mkdir bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi

        mkdir -p "bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi"
   
common.mkdir bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off

        mkdir -p "bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off"
   
common.mkdir bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off

        mkdir -p "bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off"
   
common.mkdir bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi

        mkdir -p "bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi"
   
gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/lockpool.o

    "armv6j-hardfloat-linux-gnueabi-g++"  -ftemplate-depth-128 -O2 -pipe -march=armv6j -mfpu=vfp -mfloat-abi=hard -std=gnu++98 -finline-functions -Wno-inline -Wall -pthread -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_ATOMIC_SOURCE -DNDEBUG  -I"." -c -o "bin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/lockpool.o" "libs/atomic/src/lockpool.cpp"

libs/atomic/src/lockpool.cpp: In static member function ‘static void boost::atomics::detail::lockpool::thread_fence()’:
libs/atomic/src/lockpool.cpp:127:5: error: ‘thread_fence’ is not a member of ‘boost::atomics::detail’
     atomics::detail::thread_fence(memory_order_seq_cst);
     ^
libs/atomic/src/lockpool.cpp: In static member function ‘static void boost::atomics::detail::lockpool::signal_fence()’:
libs/atomic/src/lockpool.cpp:138:5: error: ‘signal_fence’ is not a member of ‘boost::atomics::detail’
     atomics::detail::signal_fence(memory_order_seq_cst);
     ^
...skipped <pbin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi>libboost_atomic.so.1.56.0 for lack of <pbin.v2/libs/atomic/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi>lockpool.o...
gcc.compile.c++ bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/error_code.o

    "armv6j-hardfloat-linux-gnueabi-g++"  -ftemplate-depth-128 -O2 -pipe -march=armv6j -mfpu=vfp -mfloat-abi=hard -std=gnu++98 -finline-functions -Wno-inline -Wall -pedantic -pthread -fPIC  -DBOOST_ALL_NO_LIB=1 -DBOOST_SYSTEM_DYN_LINK=1 -DNDEBUG  -I"." -c -o "bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/error_code.o" "libs/system/src/error_code.cpp"

gcc.link.dll bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/libboost_system.so.1.56.0

    "armv6j-hardfloat-linux-gnueabi-g++"    -o "bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/libboost_system.so.1.56.0" -Wl,-h -Wl,libboost_system.so.1.56.0 -shared -Wl,--start-group "bin.v2/libs/system/build/gcc-4.8/gentoorelease/boost.locale.icu-off/pch-off/threading-multi/error_code.o"  -Wl,-Bstatic  -Wl,-Bdynamic -lrt -Wl,--end-group -Wl,-O1 -Wl,--as-needed -pthread

...failed updating 1 target...
 * ERROR: dev-libs/boost-1.56.0-r1::gentoo failed (compile phase):
 *   Building of Boost libraries failed
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 4141:  Called multilib-minimal_src_compile
 *   environment, line 2300:  Called multilib_foreach_abi 'multilib-minimal_abi_src_compile'
 *   environment, line 2524:  Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
 *   environment, line 2179:  Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_compile'
 *   environment, line 2177:  Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_compile'
 *   environment, line  392:  Called multilib-minimal_abi_src_compile
 *   environment, line 2294:  Called multilib_src_compile
 *   environment, line 2778:  Called python_foreach_impl 'building'
 *   environment, line 3584:  Called multibuild_foreach_variant '_python_multibuild_wrapper' 'building'
 *   environment, line 2179:  Called _multibuild_run '_python_multibuild_wrapper' 'building'
 *   environment, line 2177:  Called _python_multibuild_wrapper 'building'
 *   environment, line  487:  Called building
 *   environment, line 2748:  Called die
 * The specific snippet of code:
 *           ejam ${OPTIONS} ${PYTHON_OPTIONS} || die "Building of Boost libraries failed";



EDIT/UPDATE: After many tests to compile with/without distcc changing configuration for the number of processors available, etc. I conclude it is IMPOSSIBLE to compile dev-libs/boost-1.56.0-r1 on the Raspberry Pi alone or even using one or more other compile servers with distcc.

Anyone out there succeeded to compile it? How? Let us know.

_________________
Achille Talon Hop!


Last edited by AchilleTalon on Thu Sep 03, 2015 12:25 pm; edited 1 time in total
Back to top
View user's profile Send private message
MaverrickTM
n00b
n00b


Joined: 01 Aug 2010
Posts: 6
Location: /home/MaverrickTM

PostPosted: Mon Aug 31, 2015 11:27 am    Post subject: Reply with quote

Hi,

try to install the package alone (MAKEOPTS="-j1" emerge -1 dev-libs/boost) with "-j1". Not sure about distcc - maybe you should try without distcc.


BG Mav
_________________
Chaos ist nur eine Form der Ordnung die wir verlernt haben!
Back to top
View user's profile Send private message
Hu
Watchman
Watchman


Joined: 06 Mar 2007
Posts: 9542

PostPosted: Tue Sep 01, 2015 1:17 am    Post subject: Reply with quote

OP posted an actual compile error, not a resource exhaustion issue. Switching to MAKEOPTS=-j1 will not fix a compile error.

The atomics library is platform-dependent. That version of Boost may not have working support for ARM. OP: please try the latest boost or configure Boost not to build the atomics library.
Back to top
View user's profile Send private message
schorsch_76
Guru
Guru


Joined: 19 Jun 2012
Posts: 373

PostPosted: Tue Sep 01, 2015 7:23 am    Post subject: Reply with quote

It seems to me, that this is a bug on boost upstream. I use boost very often. Arm is not as heavily tested as x86/x86_64. As i run gentoo on my beaglebone, i have encountered such issues too. Try to mask 1.56.0 and use a smaller version number. If that s not possible, try 1.57.0.
_________________
git daily portage tree
Web: https://portage.schorsch-tech.de/cgi-bin/cgit.cgi
git clone https://portage.schorsch-tech.de/cgi-bin/cgit.cgi/portage.git
git clone git://portage.schorsch-tech.de/portage.git
Back to top
View user's profile Send private message
Irre
Apprentice
Apprentice


Joined: 09 Nov 2013
Posts: 162
Location: Stockholm

PostPosted: Tue Sep 01, 2015 8:09 am    Post subject: Reply with quote

I built a previous version natively:
Code:
 genlop -t boost
 * dev-libs/boost

     Sat Dec 13 18:28:23 2014 >>> dev-libs/boost-1.55.0-r2
       merge time: 5 hours, 7 minutes and 28 seconds.

Back to top
View user's profile Send private message
AchilleTalon
Guru
Guru


Joined: 11 Apr 2004
Posts: 349
Location: Montreal, Quebec, Canada

PostPosted: Wed Sep 02, 2015 12:41 am    Post subject: Reply with quote

Thanks for you replies.

To clarify, I currently have dev-libs/boost-1.52.0-r7 installed. I need to upgrade to keep up with new stuff. As someone said, I tried to build with a single process (-j1) and I tried a lot of combinations of local/remote build, I increased the amount of virtual memory and it seems not to be the issue.

More likely to be a problem with the ARM support as some said. I will try to build a newer version and let you know the outcome.

Regards,
_________________
Achille Talon Hop!
Back to top
View user's profile Send private message
AchilleTalon
Guru
Guru


Joined: 11 Apr 2004
Posts: 349
Location: Montreal, Quebec, Canada

PostPosted: Thu Sep 03, 2015 12:24 pm    Post subject: Reply with quote

I successfully installed dev-libs/boost-1.57.0.

Thanks you all.
_________________
Achille Talon Hop!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum