Re: Issues... always issues..
  By: Digital Man to KK4QBN on Wed Jan 17 2018 12:58:10

 DM> This "crap" is caused by the file libsbbs.so not being where it should be.
 DM> If you run "ldd jsexec", it should tell you where it thinks libsbbs.so
 DM> should be (usually wherever you built it). If you ran "make clean" after
 DM> or moved libsbbs.so, jsexec won't know about it or be able to find it.

linux-vdso.so.1 (0x00007ffdc31d1000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007ff8af807000)
libsbbs.so => not found
libncurses.so.5 => /lib/x86_64-linux-gnu/libncurses.so.5 (0x00007ff8af5e

Then how is SBBS even starting up? I remember at one time before I was
symlinking the libs from the exec dir to their build dir SBBS would not even
run stating libsbbs.so did'nt exist..

 DM> One option is to set the LD_LIBRARY_PATH environment varible to include
 DM> your Synchronet "exec" directory, where hopefully a copy or symlink to
 DM> libsbbs.so can be found.

Will do that.. and yes, the symlink to the lib IS in the ../exec dir..

I've had this happen with the Libs themself in the exec dir. 

I started this with a clean build and moved my ctrl dir and other modified
files to thew new build so I should'nt have any issues.. I would'nt think.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
 * Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA
USA