Vote count:
0
When I build boost (with MPI support FWIW) on a Raspberry pi with gcc-4.8.2 and gfortran 4.6 I get this error. aaasadaddfsdsdfsdsdfsdffsdfsdfsdffsdfsdffsdfsdffdfsdfsffsdfsdfdfsd fwerwerwerfwesdfsfsdfsfsdffsdfdfsdgsdggsdgfsfdgsfgfdgdfghfdggdfg gddfgdfgdfgdf dgdfg dgdfgdgdfgdfgf dfgdfgdfgdfgdfg dfgdfgdfgfd dfgdfg dfgd fgdf
Reading package lists... Done
Building dependency tree
Reading state information... Done
autotools-dev is already the newest version.
build-essential is already the newest version.
g++ is already the newest version.
gfortran is already the newest version.
libbz2-dev is already the newest version.
libicu-dev is already the newest version.
libzip-dev is already the newest version.
python-dev is already the newest version.
The following packages were automatically installed and are no longer required:
libblas3gf liblapack3gf
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Building Boost.Build engine with toolset gcc... tools/build/src/engine/bin.linuxarm/b2
Detecting Python version... 2.7
Detecting Python root... /usr
Unicode/ICU support for Boost.Regex?... /usr
Backing up existing Boost.Build configuration in project-config.jam.1
Generating Boost.Build configuration in project-config.jam...
Bootstrapping is done. To build, run:
./b2
To adjust configuration, edit 'project-config.jam'.
Further information:
- Command line help:
./b2 --help
- Getting started guide:
http://ift.tt/WjxCdZ
- Boost.Build documentation:
http://ift.tt/1txTMrJ
Performing configuration checks
- 32-bit : yes (cached)
- arm : yes (cached)
- lockfree boost::atomic_flag : no (cached)
- has_icu builds : yes (cached)
- zlib : yes (cached)
- iconv (libc) : yes (cached)
- icu : yes (cached)
- x86 : no (cached)
- gcc visibility : yes (cached)
- long double support : yes (cached)
- zlib : yes (cached)
^[[D
Component configuration:
- atomic : building
- chrono : building
- container : building
- context : building
- coroutine : building
- date_time : building
- exception : building
- filesystem : building
- graph : building
- graph_parallel : building
- iostreams : building
- locale : building
- log : building
- math : building
- mpi : building
- program_options : building
- python : building
- random : building
- regex : building
- serialization : building
- signals : building
- system : building
- test : building
- thread : building
- timer : building
- wave : building
...patience...
...patience...
...patience...
...patience...
...patience...
...patience...
...found 39631 targets...
...updating 993 targets...
gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/lockpool.o
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);
^
"g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -std=c++11 -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/release/threading-multi/lockpool.o" "libs/atomic/src/lockpool.cpp"
...failed gcc.compile.c++ bin.v2/libs/atomic/build/gcc-4.8/release/threading-multi/lockpool.o...
...skipped <pbin.v2/libs/atomic/build/gcc-4.8/release/threading-multi>libboost_atomic.so.1.56.0 for lack of <pbin.v2/libs/atomic/build/gcc-4.8/release/threading-multi>lockpool.o...
...skipped <p/usr/local/boost-1.56.0/lib>libboost_atomic.so.1.56.0 for lack of <pbin.v2/libs/atomic/build/gcc-4.8/release/threading-multi>libboost_atomic.so.1.56.0...
...skipped <p/usr/local/boost-1.56.0/lib>libboost_atomic.so for lack of <p/usr/local/boost-1.56.0/lib>libboost_atomic.so.1.56.0...
Boost installation complete.
pi@raspberrypi ~/Documents/boost/boost_1_56_0 $
asked 1 min ago
Boost 1.56.0 build error on raspberry pi
Aucun commentaire:
Enregistrer un commentaire