Bitcoin Forum
November 13, 2019, 10:10:16 AM *
News: 10th anniversary art contest
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Trouble with running Daemon on Seed Node  (Read 412 times)
bitgamecoin
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
January 14, 2017, 12:22:53 PM
 #1

Running a litecoin POW clone, coin is fine. Problem is the daemon and trying to set up a seed node on linux. When i run mycoinnamd, i get the error:

error while loading shared libraries: libboost_program_options.so.1.54.0: cannot open shared object file: no such file or directory exists.

When i went to install dependencies, Boost 1.58 was automatically installed. I tried purging and uninstalling boost, downloading boost 1.54, extracting and installing and building it, but to no avail.

Is there a way for me to workaround this? Thanks
The Bitcoin Forum is turning 10 years old! Join the community in sharing and exploring the notable posts made over the years.
1573639816
Hero Member
*
Offline Offline

Posts: 1573639816

View Profile Personal Message (Offline)

Ignore
1573639816
Reply with quote  #2

1573639816
Report to moderator
1573639816
Hero Member
*
Offline Offline

Posts: 1573639816

View Profile Personal Message (Offline)

Ignore
1573639816
Reply with quote  #2

1573639816
Report to moderator
Hazard
Legendary
*
Offline Offline

Activity: 980
Merit: 1000



View Profile WWW
January 14, 2017, 02:55:58 PM
 #2

You're using a daemon that was built on another system.. Don't do that.

bitgamecoin
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
January 14, 2017, 08:16:03 PM
 #3

Could you elaborate on using a daemon such as that? Thanks
Chicago
Sr. Member
****
Offline Offline

Activity: 574
Merit: 259


View Profile
January 21, 2017, 05:56:29 PM
 #4

Hello,

    Your workflow should include building a static version of the coin daemon for the seednode and hopefully have STATIC=1, PIE=1 and USE_UPNP:=- in the makefile.unix file on a hardened toolchain.
    This will help you to ensure all of the dependencies are statically linked so that your package manager doesn't end up leaving you in a position down the road where a missing file breaks the binary's ability to execute.

    Run ' ldd ' on the executable you have to see how it is dynamically linked at present and you will know all of the required files at runtime.

    Your goal should be to satisfy all of the dependencies at build time such that the only runtime dependency is the coin daemon's executable.  This is easily accomplished with static libraries for the dependencies and a statically linked coin daemon executable.

    In other words, you have some work to do, preparing a proper toolchain on the target system (seednode) and some compiling to perform.
    You could conceptually make a build box where you do all of the work there and then have the seednode be a paired down version of it with just the bare essentials.
    Just don't fall into the trap of having the coin daemon compiled on a completely different system with an entirely different toolchain, where there is great variance between the GNU libraries and other dependencies and then go to run the coin daemon by copying it onto another system.

    Your ideal situation is a build box which is nearly identical to the seednode with the exception of having the additional sources available and additional libraries required for compilation.
    If you compile with STATIC=1 within makefile.unix, you will not need to have the shared object files on the seednode.

Best Regards,
-Chicago
Kray
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
January 21, 2017, 09:23:08 PM
 #5

You're using a daemon that was built on another system.. Don't do that.

Why not to do that? Is it will create soft fork?
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!