TZUTC: -0800   
   MSGID: 57205.sync_sys@1:103/705 2befa701   
   REPLY: 57204.sync_sys@1:103/705 2befa351   
   PID: Synchronet 3.20c-Linux master/c8a409788 Jan 15 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/7c614b638 Jan 16 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: libsbbs.so shared libraries not found error after new install   
     By: Mikek to Digital Man on Thu Jan 16 2025 02:53 pm   
      
    >   Re: libsbbs.so shared libraries not found error after new install   
    >   By: Digital Man to Mikek on Thu Jan 16 2025 11:54 am   
    >   
    >  >   Re: libsbbs.so shared libraries not found error after new install   
    > Hi, thanks for the quick reply,   
    > I am using symlinks   
    > I checked ldd sbbs and it expects the libsbbs.so and others in /sbbs/exec/   
    > directory.   
    > Which is where the symlink sits.   
    >   
    > /sbbs/exec $ ldd sbbs   
    >     linux-vdso.so.1 (0xbeece000)   
    >     /usr/lib/arm-linux-gnueabihf/libarmmem-${PLATFORM}.so =>   
    > /usr/lib/arm-linux-gnueabihf/libarmmem-v7l.so (0xb6f76000)   
    >     libsbbs.so => /sbbs/exec/libsbbs.so (0xb5cf2000)   
    >     libftpsrvr.so => /sbbs/exec/libftpsrvr.so (0xb5cb7000)   
    >   
    > /sbbs/exec $ ls -al libsbbs.so   
    > lrwxrwxrwx 1 sbbs sbbs 60 Jan 16 09:50 libsbbs.so ->   
    > /sbbs/repo/src/sbbs3/gcc.linux.armv7l.lib.release/libsbbs.so   
    >   
    > /sbbs/exec $ echo $LD_LIBRARY_PATH   
    > /sbbs/exec   
    >   
    > I did check the Wiki, which is where I found to set the LD_LIBRARY_PATH.   
      
   There was a *very* recent change with how the paths for the libs are embedded   
   in the binaries, so its possible there was a regression there. Normally, I   
   would expect to see the full path to the build output directory (gcc.*.lib.*)   
   in the 'ldd sbbs' results:   
      
    $ ldd gcc.linux.x64.exe.debug/sbbs | grep libsbbs   
           libsbbs.so => /home/rswindell/sbbs/src/sbbs3/gcc.linux.x   
   4.exe.debug/../gcc.linux.x64.lib.debug/libsbbs.so (0x00007f5285400000)   
      
   It's possible that finding the *symlink* in the expected directory isn't   
   enough, so setting LD_LIBRARY_PATH to point to the build output dir for the   
   lib*.so files instead would likely do the trick.   
      
   Another option would be to 'make install' instead of 'make symlinks'.   
      
    > thanks again   
      
   No problem. Just let us know how it works for ya,   
   --    
                                               digital man (rob)   
      
   Rush quote #3:   
   The men who hold high places must be the ones who start... Closer to the Heart   
   Norco, CA WX: 63.5øF, 25.0% humidity, 9 mph W wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426