1. Forum
  2. DOVE-Net
  3. Synchronet Programming C+

  • Error in DEBUG build

    From KK4QBN@VERT/KK4QBN to Digital Man on Wed Nov 22 11:16:32 2017
    Hey DM,

    Was attempting a debug build so I could try to sort the SMTP isues out with GDB

    used 'make USE_DOSEMU=1 DEBUG=1'

    almost made it unti..

    Compiling ssl.c
    Compiling ../comio/comio_nix.c
    Linking gcc.linux.x64.lib.debug/libsbbs.so
    /usr/bin/ld: /home/tim/sbbs/src/sbbs3/../../3rdp/gcc.linux.x64.debug/cl/libcl.a(init.o): unrecognized relocation (0x2a) in section `.text'
    /usr/bin/ld: final link failed: Bad value
    collect2: error: ld returned 1 exit status
    GNUmakefile:119: recipe for target 'gcc.linux.x64.lib.debug/libsbbs.so' failed make: *** [gcc.linux.x64.lib.debug/libsbbs.so] Error 1


    wish I knew what most of this means.. I catch peices here and there.. but most of it is is just a different language to me.. (yea.. lame joke right)

    --

    Tim Smith (KK4QBN)
    KK4QBN BBS

    ---
    * Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA
  • From Accession@VERT/PHARCYDE to KK4QBN on Wed Nov 22 12:18:56 2017
    Hello KK4QBN,

    On Wed Nov 22 2017 11:16:32, KK4QBN wrote to Digital Man:

    used 'make USE_DOSEMU=1 DEBUG=1'

    almost made it unti..

    Compiling ssl.c
    Compiling ../comio/comio_nix.c
    Linking gcc.linux.x64.lib.debug/libsbbs.so
    /usr/bin/ld: /home/tim/sbbs/src/sbbs3/../../3rdp/gcc.linux.x64.debug/cl/libcl.a(ini t.o): unrecognized relocation (0x2a) in section `.text' /usr/bin/ld:
    final link failed: Bad value
    collect2: error: ld returned 1 exit status
    GNUmakefile:119: recipe for target
    'gcc.linux.x64.lib.debug/libsbbs.so' failed
    make: *** [gcc.linux.x64.lib.debug/libsbbs.so] Error 1

    If you were previously using a release build, you could try running "make clean" before compiling. I'm fairly certain that tidbit is on the wiki for upgrading on Linux.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
    Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From KK4QBN@VERT/KK4QBN to Accession on Wed Nov 22 17:17:58 2017
    Re: Error in DEBUG build
    By: Accession to KK4QBN on Wed Nov 22 2017 12:18:56

    'gcc.linux.x64.lib.debug/libsbbs.so' failed
    make: *** [gcc.linux.x64.lib.debug/libsbbs.so] Error 1

    If you were previously using a release build, you could try running "make clean" before compiling. I'm fairly certain that tidbit is on the wiki for upgrading on Linux.

    Yes, I did a make clean, I will try again later tonight.. I built the last code sudo, and run a regular make clean, that could be gicing the issue.. I don't know why, because everything belongs to the same un/ug but I'll check and see.

    Thanks for the tip.

    --

    Tim Smith (KK4QBN)
    KK4QBN BBS

    ---
    * Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA
  • From Digital Man@VERT to KK4QBN on Wed Nov 22 18:56:08 2017
    Re: Error in DEBUG build
    By: KK4QBN to Digital Man on Wed Nov 22 2017 11:16 am

    Hey DM,

    Was attempting a debug build so I could try to sort the SMTP isues out with GDB

    used 'make USE_DOSEMU=1 DEBUG=1'

    almost made it unti..

    Compiling ssl.c
    Compiling ../comio/comio_nix.c
    Linking gcc.linux.x64.lib.debug/libsbbs.so
    /usr/bin/ld: /home/tim/sbbs/src/sbbs3/../../3rdp/gcc.linux.x64.debug/cl/libcl.a(init.o): unrecognized relocation (0x2a) in section `.text'
    /usr/bin/ld: final link failed: Bad value

    It's funny, I just hit that problem with a work project. It's a well known issue:
    https://lists.gnu.org/archive/html/discuss-gnustep/2016-01/msg00021.html

    wish I knew what most of this means.. I catch peices here and there.. but most of it is is just a different language to me.. (yea.. lame joke right)

    See http://wiki.synchro.net/install:nix#clean_rebuild for details.

    digital man

    This Is Spinal Tap quote #7:
    Nigel Tufnel: That's just nitpicking, isn't it?
    Norco, CA WX: 81.7F, 23.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Accession@VERT/PHARCYDE to KK4QBN on Thu Nov 23 00:13:52 2017
    Hello KK4QBN,

    On Wed Nov 22 2017 17:17:58, KK4QBN wrote to Accession:

    If you were previously using a release build, you could try
    running "make clean" before compiling. I'm fairly certain that
    tidbit is on the wiki for upgrading on Linux.

    Yes, I did a make clean, I will try again later tonight.. I built the
    last code sudo, and run a regular make clean, that could be gicing the issue.. I don't know why, because everything belongs to the same un/ug
    but I'll check and see.

    If your name/group is your user, and you only start the sbbs daemon with sudo, you should probably compile as the user, and not with sudo (as long as it's in a directory that you can do so, ie: /sbbs would require sudo, but /home/bbs/sbbs or /home/sbbs or some such you would be able to).

    All sudo is used for in that case would be to bind to ports lower than 1024.

    Thanks for the tip.

    No problem. Also, if you've done some with sudo and some without, you may want to double check your permissions, up to and including the binaries in your release and debug directories to make sure they match your user/group. Otherwise a simple "chown -R user:group /sbbs" would do the trick also, but that part I'm sure you knew. I was just reminding you to check the directories you've compiled any new binaries in.

    I just recompiled the code a few days ago without issue here, and I don't think
    there's been any updates in regards to the file mentioned in your error. So I'm
    guessing it's just cleaning out the release build. You may have to continue to follow the wiki in regards to manually cleaning out some, if not all of those directories. Besides actual bugs found and fixed, changing from release to debug or vise versa is usually where I've come across the most issues, but so far every time doing the full clean via the wiki has worked in the past.

    Now I just run debug all the time. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
    Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
  • From KK4QBN@VERT/KK4QBN to Accession on Thu Nov 23 08:17:51 2017
    Re: Error in DEBUG build
    By: Accession to KK4QBN on Thu Nov 23 2017 00:13:52

    No problem. Also, if you've done some with sudo and some without, you may want to double check your permissions, up to and including the binaries in your release and debug directories to make sure they match your user/group. Otherwise a simple "chown -R user:group /sbbs" would do the trick also, but that part I'm sure you knew. I was just reminding you to check the directories you've compiled any new binaries in.

    I do really believe thats what the issue is, I'll need to go back over it again and make sure.. I usually miss something somewhere or do something unintentionly small that screws stuff up in a big way :)

    --

    Tim Smith (KK4QBN)
    KK4QBN BBS

    ---
    * Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA
  • From Accession@VERT/PHARCYDE to KK4QBN on Thu Nov 23 09:45:24 2017
    Hello KK4QBN,

    On Thu Nov 23 2017 08:17:50, KK4QBN wrote to Accession:

    No problem. Also, if you've done some with sudo and some without,
    you may want to double check your permissions, up to and
    including the binaries in your release and debug directories to
    make sure they match your user/group. Otherwise a simple "chown
    -R user:group /sbbs" would do the trick also, but that part I'm
    sure you knew. I was just reminding you to check the directories
    you've compiled any new binaries in.

    I do really believe thats what the issue is, I'll need to go back over
    it again and make sure.. I usually miss something somewhere or do something unintentionly small that screws stuff up in a big way :)

    You're not the only one. Permissions have always been (and probably always will
    be) one of the biggest issues with running a BBS on Linux. Even something as small as editing an ansi as a different user will most likely cause that ansi not to display or an error to occur. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
    Synchronet thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)