Re: Re: upgrading linux sbbs
By: Digital Man to Hemo on Mon Nov 21 2016 11:37 pm

Re: Re: upgrading linux sbbs
By: Hemo to Digital Man on Mon Nov 21 2016 10:51 pm

Digital Man wrote to Hemo <=-

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

<snip>

gmake: *** [smblib] Error 2

<snip>

From the frying pan to the fire. Something with the new voting
code is unappreciated on my box. :(

<snip>

Looking more closely at your errors now, I don't think my original analysis was correct: you do have the latest code from CVS.

However, that code does not appear to be compatible with your C compiler. What C compiler (and version) are you using?

Assuming gcc, you can query the version by typing 'gcc -v' then copy and paste that output here.
I've begun using anonymous unions and structs which are newer C language feature. We have to add some command-line options to enable these feature in your version GCC.

After some digging I think I've got it figured out. I was able to install a newer development chain (gcc 4.9.2) and adding -ltinfo to LDFLAGS I am running v3.17a.

The actual steps to get this done took less time than writing this reply. Researching it took a few drinks.

I'm off to see what I else I can break.

thank you.

-- Hemo

... Whatever it is, it won't work.

---
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: Re: upgrading linux sbbs
By: Hemo to Digital Man on Mon Nov 28 2016 08:54 pm

Re: Re: upgrading linux sbbs
By: Digital Man to Hemo on Mon Nov 21 2016 11:37 pm

Re: Re: upgrading linux sbbs
By: Hemo to Digital Man on Mon Nov 21 2016 10:51 pm

Digital Man wrote to Hemo <=-

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

<snip>

gmake: *** [smblib] Error 2

<snip>

From the frying pan to the fire. Something with the new voting
code is unappreciated on my box. :(

<snip>

Looking more closely at your errors now, I don't think my original analysis was correct: you do have the latest code from CVS.

However, that code does not appear to be compatible with your C compiler. What C compiler (and version) are you using?

Assuming gcc, you can query the version by typing 'gcc -v' then copy and paste that output here.
I've begun using anonymous unions and structs which are newer C language feature. We have to add some command-line options to enable these feature in your version GCC.

After some digging I think I've got it figured out. I was able to install a newer development chain (gcc 4.9.2) and adding -ltinfo to LDFLAGS I am running v3.17a.

Interesting. I wonder why -ltinfo was required.

The actual steps to get this done took less time than writing this reply. Researching it took a few drinks.

I'm off to see what I else I can break.

Okay. I think there's probably a way through the -std command-line argument to get the current (new) code to compile with old version of GCC, but an upgrade is another option. :-)

digital man

Synchronet/BBS Terminology Definition #51:
TCP = Transmission Control Protocol
Norco, CA WX: 50.4oF, 85.0% humidity, 2 mph S wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Digital Man wrote to Hemo <=-

Re: Re: upgrading linux sbbs
By: Hemo to Digital Man on Mon Nov 28 2016 08:54 pm

<snip>

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

<snip>

gmake: *** [smblib] Error 2

<snip>

Looking more closely at your errors now, I don't think my original analysis was correct: you do have the latest code from CVS.

However, that code does not appear to be compatible with your C compiler. What C compiler (and version) are you using?

Assuming gcc, you can query the version by typing 'gcc -v' then copy and paste that output here.
I've begun using anonymous unions and structs which are newer C language feature. We have to add some command-line options to enable these feature in your version GCC.

After some digging I think I've got it figured out. I was able to install a newer development chain (gcc 4.9.2) and adding -ltinfo to LDFLAGS I am running v3.17a.

Interesting. I wonder why -ltinfo was required.

In the grand scope of things, I'm still pretty green at C, makefiles, and linking. I know enough to get by and sometimes to get myself where I shouldn't be.

I tried researching what some of the command line options would be to compile with the older version, didn't get far, and then stumbled on a 'simple' method to install the newer compiler and libraries, and still maintain the old ones - being able to switch between them. I tried the newer method and got past the compile, but then it stumbled during linking with an error: undefined reference to symbol 'halfdelay' and //lib64/libtinfo.so.5: error adding symbols: DSO missing from command line

A search later and I found an article at stackoverflow talking about libncurses is linked to libtinfo, so the linker looks there, -but- the newer compiler might be running with '--as-needed' and/or '--no-copy-dt-needed-entries' which might cause the issue I had, so I exported LDFLAGS="-ltinfo" prior to the compile and it all seemed happy.

The actual steps to get this done took less time than writing this reply. Researching it took a few drinks.

I'm off to see what I else I can break.

Okay. I think there's probably a way through the -std command-line argument to get the current (new) code to compile with old version of
GCC, but an upgrade is another option. :-)

Again, I'm pretty green at this, rely on GIYF for things beyond my scope, which worked for me this time by virtue of taking the longer road. After going through all this, I found references to using -fms-extensions to enable anonymous unions/structs in gcc v 4.4.7. Trying to test that out now...


... Gone crazy, be back later, please leave message.
--- MultiMail/Win64 v0.73
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Followed the steps at http://wiki.synchro.net/install:nix regarding updating.

Didn't get any errors during the CVS pull or the gmake, and have tried with
and without the RELEASE=1 flag, same results..

I'm trying to get the bleeding edge 3.17 version, am I not doing things correctly to get that? Do I need to specify CVSTAG=sbbs317 (or similar) when I do a make ?

tia

- Hemo

... It is better to know some of the questions than all of the answers.

---
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Hemo to All on Wed Nov 16 2016 02:34 pm

Followed the steps at http://wiki.synchro.net/install:nix regarding updating.

Didn't get any errors during the CVS pull or the gmake, and have tried with and without the RELEASE=1 flag, same results..

No errors = good results, no?

I'm trying to get the bleeding edge 3.17 version, am I not doing things correctly to get that? Do I need to specify CVSTAG=sbbs317 (or similar) when I do a make ?

No, there is no tag for sbbs317 (it hasn't been "released" yet). Is there a problem?

digital man

Synchronet "Real Fact" #31:
The Synchronet IRC server (ircd) was written in JS by Randy Sommerfeld (Cyan). Norco, CA WX: 60.3oF, 83.0% humidity, 4 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

---
* Synchronet * Freeway BBS in Bendigo, Australia.
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Hello Hemo,

On 16 Nov 16 14:34, Hemo wrote to All:

Followed the steps at http://wiki.synchro.net/install:nix regarding updating.

Didn't get any errors during the CVS pull or the gmake, and have tried with and without the RELEASE=1 flag, same results..

I believe "with and without" the RELEASE=1 flag does the exact same thing. Using DEBUG=1 instead would give you a debug version in which you can use gdb in order to find out why things aren't working or crashed at some point.

I'm trying to get the bleeding edge 3.17 version, am I not doing
things correctly to get that? Do I need to specify CVSTAG=sbbs317 (or similar) when I do a make ?

Nope, what you did above should be all you need for the latest CVS sources (ie:

3.17). The CVS tags are only for specific older versions.

Is there a specific reason as to why you /don't/ think you have the latest sources compiled? Is something telling you differently?

Regards,
Nick

... "-Y-| -+-+-#-A. -> -+-|-|-U-i -e-+-+-i-|-+ -C-#-#-+-e-#-A."
--- GoldED+/LNX 1.1.5-b20160827
# Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
* Synchronet * thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Digital Man to Hemo on Wed Nov 16 2016 06:07 pm

Re: upgrading linux sbbs
By: Hemo to All on Wed Nov 16 2016 02:34 pm

Didn't get any errors during the CVS pull or the gmake, and have tried
with and without the RELEASE=1 flag, same results..

No errors = good results, no?

I think so. the programs compile and I'm running them.

I'm trying to get the bleeding edge 3.17 version, am I not doing
things correctly to get that? Do I need to specify CVSTAG=sbbs317 (or
similar) when I do a make ?

No, there is no tag for sbbs317 (it hasn't been "released" yet). Is there a problem?

I guess I might be confused by the info at a connect/login:
Synchronet BBS for Linux Version 3.16 <--- I expected this to be 3.17

The point I failed to present in my previous email is that all references still report version 3.16 when connecting or viewing system info. If that is normal for v3.17 until is is official, then I think I'm good.

I'm just confused by the version display I guess.

--Hemo

... You know you're getting old when the candles cost more than the cake.

---
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Hemo to Digital Man on Thu Nov 17 2016 01:11 pm

Re: upgrading linux sbbs
By: Digital Man to Hemo on Wed Nov 16 2016 06:07 pm

Re: upgrading linux sbbs
By: Hemo to All on Wed Nov 16 2016 02:34 pm

Didn't get any errors during the CVS pull or the gmake, and have tried
with and without the RELEASE=1 flag, same results..

No errors = good results, no?

I think so. the programs compile and I'm running them.

I'm trying to get the bleeding edge 3.17 version, am I not doing
things correctly to get that? Do I need to specify CVSTAG=sbbs317 (or
similar) when I do a make ?

No, there is no tag for sbbs317 (it hasn't been "released" yet). Is there a problem?

I guess I might be confused by the info at a connect/login:
Synchronet BBS for Linux Version 3.16 <--- I expected this to be 3.17

The point I failed to present in my previous email is that all references still report version 3.16 when connecting or viewing system info. If that is normal for v3.17 until is is official, then I think I'm good.

I'm just confused by the version display I guess.

No, it should be displaying "Version 3.17". It sounds like the 'sbbs' you're running is not the same 'sbbs' that you're building. You did restart 'sbbs' after you cvs-updated and built, right? If yes, then double-check your file system for multiple copies of sbbs and libsbbs.so and that should help to clarify what's going on (e.g. maybe you're running a release build, but built a debug build?).

digital man

Synchronet/BBS Terminology Definition #26:
FTSC = FidoNet Technical Standards Committee
Norco, CA WX: 67.3oF, 13.0% humidity, 10 mph SW wind, 0.00 inches rain/24hrs --- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Digital Man to Hemo on Thu Nov 17 2016 13:21:18

No, it should be displaying "Version 3.17". It sounds like the 'sbbs' you're running is not the same 'sbbs' that you're building. You did restart 'sbbs' after you cvs-updated and built, right? If yes, then

At one time, for some reason, I checked Synchronet out using the 3.16 tag, and had to do a bunch of CVS jiggerypokery before I could move on to 3.17. I wonder if that's what's going on here (and what I had to do to get around it, which I no longer remember).

---
echicken
electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230
* Synchronet * electronic chicken bbs - bbs.electronicchicken.com
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Digital Man to Hemo on Thu Nov 17 2016 01:21 pm

Re: upgrading linux sbbs

By: Digital Man to Hemo on Wed Nov 16 2016 06:07 pm
I guess I might be confused by the info at a connect/login:
Synchronet BBS for Linux Version 3.16 <--- I expected this to be

3.17

No, it should be displaying "Version 3.17". It sounds like the 'sbbs' you're running is not the same 'sbbs' that you're building. You did restart 'sbbs' after you cvs-updated and built, right? If yes, then double-check your file system for multiple copies of sbbs and libsbbs.so and that should help to clarify what's going on (e.g. maybe you're running a release build, but built a debug build?).

checked - only sbbs is the one I am running from /sbbs/exec/sbbs which is symlinked to /sbbs/src/sbbs3/gcc.linux.x64.exe.release/sbbs

so.. here is something strange.. after running the cvs update commands, I note the most recent file under /sbbs/src/sbbs3 is addfiles.c and addfiles.d, dated June 7, 2016. The next most recent file is main.cpp, dated August 15, 2015:

ls -rtl /sbbs/src/sbbs3

-rw-rw-r--. 1 sbbs sbbs 15344 Jul 28 2015 wordwrap.c
-rw-rw-r--. 1 sbbs sbbs 47696 Aug 15 2015 sbbsdefs.h
-rw-rw-r--. 1 sbbs sbbs 164785 Aug 15 2015 main.cpp
... directory entries removed ...
-rw-rw-r--. 1 sbbs sbbs 25851 Jun 7 00:54 addfiles.c
-rw-rw-r--. 1 sbbs sbbs 1641 Jun 7 00:54 addfiles.d

It appears I am not obtaining the most recent files with the cvs update command?

--Hemo

... We think he's dead, but we're afraid to ask.

---
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 01:23 pm

Re: upgrading linux sbbs
By: Digital Man to Hemo on Thu Nov 17 2016 01:21 pm

Re: upgrading linux sbbs

By: Digital Man to Hemo on Wed Nov 16 2016 06:07 pm
I guess I might be confused by the info at a connect/login:
Synchronet BBS for Linux Version 3.16 <--- I expected this to be

3.17

No, it should be displaying "Version 3.17". It sounds like the 'sbbs' you're running is not the same 'sbbs' that you're building. You did restart 'sbbs' after you cvs-updated and built, right? If yes, then double-check your file system for multiple copies of sbbs and libsbbs.so and that should help to clarify what's going on (e.g. maybe you're running a release build, but built a debug build?).

checked - only sbbs is the one I am running from /sbbs/exec/sbbs which is symlinked to /sbbs/src/sbbs3/gcc.linux.x64.exe.release/sbbs

so.. here is something strange.. after running the cvs update commands, I note the most recent file under /sbbs/src/sbbs3 is addfiles.c and addfiles.d, dated June 7, 2016. The next most recent file is main.cpp, dated August 15, 2015:

ls -rtl /sbbs/src/sbbs3

-rw-rw-r--. 1 sbbs sbbs 15344 Jul 28 2015 wordwrap.c
-rw-rw-r--. 1 sbbs sbbs 47696 Aug 15 2015 sbbsdefs.h
-rw-rw-r--. 1 sbbs sbbs 164785 Aug 15 2015 main.cpp
... directory entries removed ...
-rw-rw-r--. 1 sbbs sbbs 25851 Jun 7 00:54 addfiles.c
-rw-rw-r--. 1 sbbs sbbs 1641 Jun 7 00:54 addfiles.d

It appears I am not obtaining the most recent files with the cvs update command?

Sounds like you might be pinned to a tag (label)? If this is the case, try running "cvs update -d -A" from your "src" and "3rdp" directories (or their parent directory).

digital man

Synchronet "Real Fact" #90:
Synchronet/DSZ "hack" of '93: http://wiki.synchro.net/history:hack93
Norco, CA WX: 75.3oF, 7.0% humidity, 6 mph SSW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Digital Man to Hemo on Fri Nov 18 2016 02:12 pm

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 01:23 pm

Sounds like you might be pinned to a tag (label)? If this is the case, try running "cvs update -d -A" from your "src" and "3rdp" directories (or their parent directory).

Well, that seemed to do something. I lot of 'move away' of files because 'it is in the way', and then it looks like new copies pulled.

Now I have compile errors...

[sbbs@bbs.ujoint.org sbbs3]$ cd /sbbs/src/sbbs3; gmake RELEASE=1
gmake -C /home/sbbs/src/sbbs3/../../3rdp/build jslib
gmake[1]: Entering directory `/home/sbbs/3rdp/build'
gmake[1]: Nothing to be done for `jslib'.
gmake[1]: Leaving directory `/home/sbbs/3rdp/build'
gmake -C /home/sbbs/src/sbbs3/../smblib lib
gmake[1]: Entering directory `/home/sbbs/src/smblib'
Compiling smblib.c
In file included from smblib.h:68,
from smblib.c:49:
smbdefs.h:436: warning: declaration does not declare anything
smbdefs.h:440: warning: declaration does not declare anything
smbdefs.h:441: warning: declaration does not declare anything
smblib.c: In function `smb_init_idx':
smblib.c:1634: error: `idxrec_t' has no member named `subj'
smblib.c:1638: error: `idxrec_t' has no member named `to'
smblib.c:1640: error: `idxrec_t' has no member named `to'
smblib.c:1642: error: `idxrec_t' has no member named `from'
smblib.c:1644: error: `idxrec_t' has no member named `from'
smblib.c:1646: error: `idxrec_t' has no member named `votes'
smblib.c:1647: error: `idxrec_t' has no member named `remsg'
smblib.c:1649: error: `idxrec_t' has no member named `to'
smblib.c:1650: error: `idxrec_t' has no member named `from'
smblib.c: In function `smb_voted_already':
smblib.c:1699: error: `idxrec_t' has no member named `remsg'
gmake[1]: *** [gcc.linux.x64.obj.release/smblib.o] Error 1
gmake[1]: Leaving directory `/home/sbbs/src/smblib'
gmake: *** [smblib] Error 2


From the frying pan to the fire. Something with the new voting code is unappreciated on my box. :(

-- Hemo

---
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

Re: upgrading linux sbbs
By: Digital Man to Hemo on Fri Nov 18 2016 02:12 pm

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 01:23 pm

Sounds like you might be pinned to a tag (label)? If this is the case, try running "cvs update -d -A" from your "src" and "3rdp" directories (or their parent directory).

Well, that seemed to do something. I lot of 'move away' of files because 'it is in the way', and then it looks like new copies pulled.

Now I have compile errors...

[sbbs@bbs.ujoint.org sbbs3]$ cd /sbbs/src/sbbs3; gmake RELEASE=1
gmake -C /home/sbbs/src/sbbs3/../../3rdp/build jslib
gmake[1]: Entering directory `/home/sbbs/3rdp/build'
gmake[1]: Nothing to be done for `jslib'.
gmake[1]: Leaving directory `/home/sbbs/3rdp/build'
gmake -C /home/sbbs/src/sbbs3/../smblib lib
gmake[1]: Entering directory `/home/sbbs/src/smblib'
Compiling smblib.c
In file included from smblib.h:68,
from smblib.c:49:
smbdefs.h:436: warning: declaration does not declare anything
smbdefs.h:440: warning: declaration does not declare anything
smbdefs.h:441: warning: declaration does not declare anything
smblib.c: In function `smb_init_idx':
smblib.c:1634: error: `idxrec_t' has no member named `subj'
smblib.c:1638: error: `idxrec_t' has no member named `to'
smblib.c:1640: error: `idxrec_t' has no member named `to'
smblib.c:1642: error: `idxrec_t' has no member named `from'
smblib.c:1644: error: `idxrec_t' has no member named `from'
smblib.c:1646: error: `idxrec_t' has no member named `votes'
smblib.c:1647: error: `idxrec_t' has no member named `remsg'
smblib.c:1649: error: `idxrec_t' has no member named `to'
smblib.c:1650: error: `idxrec_t' has no member named `from'
smblib.c: In function `smb_voted_already':
smblib.c:1699: error: `idxrec_t' has no member named `remsg'
gmake[1]: *** [gcc.linux.x64.obj.release/smblib.o] Error 1
gmake[1]: Leaving directory `/home/sbbs/src/smblib'
gmake: *** [smblib] Error 2

From the frying pan to the fire. Something with the new voting code is unappreciated on my box. :(

In what directory did you run "cvs update -d -A"? It looks like you don't have the latest files from src/smblib, which implies you did not run "cvs update -d -A" from the "src" directory.

digital man

Synchronet/BBS Terminology Definition #15:
DOS = Disk Operating System (as in PC-DOS and MS-DOS)
Norco, CA WX: 61.8oF, 16.0% humidity, 7 mph W wind, 0.00 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Digital Man wrote to Hemo <=-

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

gmake: *** [smblib] Error 2

From the frying pan to the fire. Something with the new voting code is unappreciated on my box. :(

In what directory did you run "cvs update -d -A"? It looks like you
don't have the latest files from src/smblib, which implies you did not
run "cvs update -d -A" from the "src" directory.

Oy.

I followed the instructions at http://wiki.synchro.net/install:nix stating I should be in the /sbbs folder when doing the cvs update command. You commented I should run the command from the src and 3rdp directories or their parent, so I just ran it from /sbbs, which is the parent to both /sbbs/src and /sbbs/3rdp.

I'm willing to try things, so I just ran 'cvs update -d -A' again from both /sbbs/src and /sbbs/3rdp. Then I changed to /sbbs/src/sbbs3 and issue the command 'gmake RELEASE=1'. Same bloody results.

Now I'm grasping.. I am following the instructions but it doesn't work, so I started trying some other things. I figure I'll fix it, I back up /sbbs/src/smblib and then remove the directory, I no longer have /sbbs/src/smblib. I run the 'cvs update -d -A' command again from /sbbs/src and sbbs/3rdp, and I now have a fresh new /sbbs/src/smblib folder populated with new files, so I know the entire smblib folder is freshly pulled from the cvsupdate command. I run gmake and get the same dang results again.

I give. Maybe it's the universe giving me signals or something, I don't know.
Ugh.

Thanks for the assistance thus far.

-- Hemo





... 2 + 2 = 5 for extremely large values of 2.
--- MultiMail/Win32 v0.49
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Re: Re: upgrading linux sbbs
By: Hemo to Digital Man on Mon Nov 21 2016 10:51 pm

Digital Man wrote to Hemo <=-

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

gmake: *** [smblib] Error 2

From the frying pan to the fire. Something with the new voting code is unappreciated on my box. :(

In what directory did you run "cvs update -d -A"? It looks like you don't have the latest files from src/smblib, which implies you did not run "cvs update -d -A" from the "src" directory.

Oy.

I followed the instructions at http://wiki.synchro.net/install:nix stating I should be in the /sbbs folder when doing the cvs update command. You commented I should run the command from the src and 3rdp directories or their parent, so I just ran it from /sbbs, which is the parent to both /sbbs/src and /sbbs/3rdp.

I'm willing to try things, so I just ran 'cvs update -d -A' again from both /sbbs/src and /sbbs/3rdp. Then I changed to /sbbs/src/sbbs3 and issue the command 'gmake RELEASE=1'. Same bloody results.

Now I'm grasping.. I am following the instructions but it doesn't work, so I started trying some other things. I figure I'll fix it, I back up /sbbs/src/smblib and then remove the directory, I no longer have /sbbs/src/smblib. I run the 'cvs update -d -A' command again from /sbbs/src and sbbs/3rdp, and I now have a fresh new /sbbs/src/smblib folder populated with new files, so I know the entire smblib folder is freshly pulled from the cvsupdate command. I run gmake and get the same dang results again.

I give. Maybe it's the universe giving me signals or something, I don't know.
Ugh.

Looking more closely at your errors now, I don't think my original analysis was correct: you do have the latest code from CVS.

However, that code does not appear to be compatible with your C compiler. What C compiler (and version) are you using?

Assuming gcc, you can query the version by typing 'gcc -v' then copy and paste that output here.

I've begun using anonymous unions and structs which are newer C language feature. We have to add some command-line options to enable these feature in your version GCC.

digital man

Synchronet/BBS Terminology Definition #29:
IP = Internet Protocol
Norco, CA WX: 53.9oF, 91.0% humidity, 1 mph NW wind, 0.43 inches rain/24hrs
--- SBBSecho 3.00-Win32
* Origin: Vertrauen - vert.synchro.net (1:103/705)

On 11/21/2016 11:51 PM, Hemo wrote:

Digital Man wrote to Hemo <=-

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

gmake: *** [smblib] Error 2

From the frying pan to the fire. Something with the new voting code is unappreciated on my box. :(

In what directory did you run "cvs update -d -A"? It looks like you don't have the latest files from src/smblib, which implies you did not run "cvs update -d -A" from the "src" directory.

Oy.

I followed the instructions at http://wiki.synchro.net/install:nix stating I should be in the /sbbs folder when doing the cvs update command. You

commented

I should run the command from the src and 3rdp directories or their parent,

so

I just ran it from /sbbs, which is the parent to both /sbbs/src and

/sbbs/3rdp.

I'm willing to try things, so I just ran 'cvs update -d -A' again from both /sbbs/src and /sbbs/3rdp. Then I changed to /sbbs/src/sbbs3 and issue the command 'gmake RELEASE=1'. Same bloody results.

I usually build debug and for some reason, I assumed if I didnt use
RELEASE=1, I was building debug.

However, I think if you do the Quick Install from CVS (http://wiki.synchro.net/install:nix) the default build RELEASE.

Anyways, I guess I had built release initially and then was trying
update debug and things started getting weird until I figured that out.

I ended up scrapping the whole thing and starting over with a fresh
DEBUG=1 build. I think..

-Mindless Automaton
---
* Synchronet * Eldritch Clockwork BBS - eldritch.darktech.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)

Digital Man wrote to Hemo <=-

Re: Re: upgrading linux sbbs
By: Hemo to Digital Man on Mon Nov 21 2016 10:51 pm

Digital Man wrote to Hemo <=-

Re: upgrading linux sbbs
By: Hemo to Digital Man on Fri Nov 18 2016 10:46 pm

gmake: *** [smblib] Error 2

(snipped)
the cvsupdate command. I run gmake and get the same dang results again.

I give. Maybe it's the universe giving me signals or something, I don't know.
Ugh.

Looking more closely at your errors now, I don't think my original analysis was correct: you do have the latest code from CVS.

However, that code does not appear to be compatible with your C
compiler. What C compiler (and version) are you using?

Assuming gcc, you can query the version by typing 'gcc -v' then copy
and paste that output here.

I'm on CentOS 6.8 x86_64, gcc listed 4.4.7:

[sbbs@bbs.ujoint.org ~]$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC)


I'll try updating later tonight and see if I get any update to gcc or other development tools.


... Direct from the Ministry of Silly Walks
--- MultiMail/Win32 v0.49
* Synchronet * - Running madly into the wind and screaming - bbs.ujoint.org
* Origin: Vertrauen - vert.synchro.net (1:103/705)