Bitcoin Forum
November 09, 2024, 10:40:36 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Help compiling bitcoin on Centos6.5  (Read 2631 times)
m3 (OP)
Sr. Member
****
Offline Offline

Activity: 460
Merit: 250


View Profile WWW
May 02, 2014, 01:47:06 AM
 #1

I have been trying to install bitcoind on centos and was not able to compile it, this is the config log:

root@[bitcoin-watchonly]# ./configure --without-qt --libdir=/usr/local/lib/
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to disable maintainer-specific portions of Makefiles... yes
checking for g++... g++
checking for C++ compiler default output file name... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking how to run the C++ preprocessor... g++ -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... gcc
checking whether we are using the GNU Objective C compiler... no
checking whether gcc accepts -g... no
checking dependency style of gcc... gcc3
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for a sed that does not truncate output... /bin/sed
checking for ar... /usr/bin/ar
checking for ranlib... /usr/bin/ranlib
checking for strip... /usr/bin/strip
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... no
checking for genhtml... no
checking for git... /usr/bin/git
checking for moc-qt4... no
checking for moc4... no
checking for moc... no
checking for uic-qt4... no
checking for uic4... no
checking for uic... no
checking for rcc-qt4... no
checking for rcc4... no
checking for rcc... no
checking for lrelease-qt4... no
checking for lrelease4... no
checking for lrelease... no
checking for lupdate-qt4... no
checking for lupdate4... no
checking for lupdate... no
checking for protoc... no
checking for ccache... no
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether the linker accepts -Wl,--large-address-aware... no
checking whether C++ compiler accepts -Wstack-protector... yes
checking whether C++ compiler accepts -fPIE... yes
checking whether C++ preprocessor accepts -D_FORTIFY_SOURCE=2... yes
checking whether the linker accepts -Wl,--dynamicbase... no
checking whether the linker accepts -Wl,--nxcompat... no
checking whether the linker accepts -Wl,-z,relro... yes
checking whether the linker accepts -Wl,-z,now... yes
checking whether C++ compiler accepts -fno-stack-protector... yes
checking whether C++ compiler accepts -fstack-protector-all... yes
checking whether the linker accepts -pie... no
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking for unistd.h... (cached) yes
checking for strings.h... (cached) yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking for MSG_NOSIGNAL... yes
checking for Berkeley DB C++ headers... /usr/src/db4.8/db-4.8.30.NC/build_unix//
checking for main in -ldb_cxx-4.8... yes
checking for main in -lminiupnpc... no
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system-mt... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem-mt... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread-mt... yes
checking whether the Boost::Chrono library is available... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
configure: error: No working boost sleep implementation found

BookLover
Hero Member
*****
Offline Offline

Activity: 533
Merit: 500


^Bitcoin Library of Congress.


View Profile
May 02, 2014, 02:06:42 AM
 #2

A similar question was asked before:
Quote from: dserrano5 link=topic=522014.msg5842619#msg5842619
I'm unable to configure 0.9.0:

Code:
$ ./configure --with-incompatible-bdb --without-gui
[…]
checking for boostlib >= 1.20.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options-mt... yes
checking whether the Boost::Thread library is available... no
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono-mt... yes
checking whether the Boost::Unit_Test_Framework library is available... yes
checking for dynamic linked boost test... yes
configure: error: No working boost sleep implementation found. If on ubuntu 13.10 with libboost1.54-all-dev remove libboost.1.54-all-dev and use libboost1.53-all-dev

This seemed to be a problem in MacOS last year according to my searches, however I'm in linux amd64 so I'm not sure whether I'm finding the same problem or not. This is Debian wheezy, with boost 1.49. I'm working with bitcoin 0.9.0 as downloaded from https://github.com/bitcoin/bitcoin/archive/v0.9.0.tar.gz. config.log is here.


It was answered here:
Quote from: wumpus link=topic=522014.msg5853753#msg5853753
Main problem from config.log is:
Code:
/usr/include/boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant
That line is probably:
Code:
TIME_UTC=1,
This causes a symbol collision in some environments with a libc++ macro.
Later boost versions changed this to TIME_UTC_.

I'm not sure what the proper way to resolve this is, apart from upgrading boost.

In any case this is a boost issue, it also appears on Google various places outside the context of building bitcoin. There are some workarounds:
- https://bbs.archlinux.org/viewtopic.php?id=144593
- https://stackoverflow.com/questions/17599377/boost-error-trouble-compiling-xtime-hpp
- https://svn.boost.org/trac/boost/ticket/6940

The solution which worked for dserrano5 was to edit xtime.hpp as suggested here:https://bbs.archlinux.org/viewtopic.php?id=144593

Hope this helps! Cheesy

fitraok09
Legendary
*
Offline Offline

Activity: 1049
Merit: 1009

TRX: TCRKDukYt2zDie9vJDhToKrP3tyTV29U48


View Profile
December 10, 2016, 01:50:08 PM
 #3


It was answered here:
Quote from: wumpus link=topic=522014.msg5853753#msg5853753
Main problem from config.log is:
Code:
/usr/include/boost/thread/xtime.hpp:23:5: error: expected identifier before numeric constant
That line is probably:
Code:
TIME_UTC=1,
This causes a symbol collision in some environments with a libc++ macro.
Later boost versions changed this to TIME_UTC_.

I'm not sure what the proper way to resolve this is, apart from upgrading boost.

In any case this is a boost issue, it also appears on Google various places outside the context of building bitcoin. There are some workarounds:
- https://bbs.archlinux.org/viewtopic.php?id=144593
- https://stackoverflow.com/questions/17599377/boost-error-trouble-compiling-xtime-hpp
- https://svn.boost.org/trac/boost/ticket/6940

The solution which worked for dserrano5 was to edit xtime.hpp as suggested here:https://bbs.archlinux.org/viewtopic.php?id=144593

Hope this helps! Cheesy

is there an other solution? way is not work properly in my ubuntu  Huh
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3542
Merit: 6886


Just writing some code


View Profile WWW
December 10, 2016, 05:47:14 PM
 #4

is there an other solution? way is not work properly in my ubuntu  Huh
Bitcoin Core has changed since 0.9.x. Just follow the instructions here: https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md to build Bitcoin Core for ubuntu.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!