Compiling ansiterm.cpp
In file included from sbbs.h:315,
from ansiterm.cpp:22:
sftp.h:47:6: error: variable or field `sftp_handle_data' declared void
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~~~~~~~~~~~~~
sftp.h:47:23: error: `sbbs_t' was not declared in this scope; did you mean `sub_t'?
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~~~
| sub_t
sftp.h:47:31: error: `sbbs' was not declared in this scope
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~
sftp.h:47:37: error: expected primary-expression before `char'
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~
sftp.h:47:50: error: expected primary-expression before `int'
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~
sbbs.h:471:9: error: `sftps_state_t' does not name a type
471 | sftps_state_t sftp_state = nullptr;
| ^~~~~~~~~~~~~
make: *** [/home/bbs/repo/src/sbbs3/../build/Common.gmake:546: gcc.linux.x64.obj.release-mt/ansiterm.o] Error 1

The frustration here is that I have set up a test system so I can make sure I can get a clean compile before trying this on the production system. So far, this strategy has not worked. I don't know what it is... the move from CVS to git, the move from 3.19 to 3.20, or something else... but getting a clean compile never used to be this difficult.

Thank goodness I take nightly backups.

---
þ Synchronet þ Capitol City Test System

Re: compile error
By: Dumas Walker to digital man on Wed May 01 2024 09:13 am

Compiling ansiterm.cpp
In file included from sbbs.h:315,
from ansiterm.cpp:22:
sftp.h:47:6: error: variable or field `sftp_handle_data' declared void
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~~~~~~~~~~~~~
sftp.h:47:23: error: `sbbs_t' was not declared in this scope; did you mean `sub_t'?
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~~~
| sub_t
sftp.h:47:31: error: `sbbs' was not declared in this scope
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~
sftp.h:47:37: error: expected primary-expression before `char'
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~~
sftp.h:47:50: error: expected primary-expression before `int'
47 | void sftp_handle_data(sbbs_t *sbbs, char *inbuf, int len);
| ^~~
sbbs.h:471:9: error: `sftps_state_t' does not name a type
471 | sftps_state_t sftp_state = nullptr;
| ^~~~~~~~~~~~~
make: *** [/home/bbs/repo/src/sbbs3/../build/Common.gmake:546: gcc.linux.x64.obj.release-mt/ansiterm.o] Error 1

The frustration here is that I have set up a test system so I can make sure I can get a clean compile before trying this on the production system. So far, this strategy has not worked. I don't know what it is... the move from CVS to git, the move from 3.19 to 3.20, or something else... but getting a clean compile never used to be this difficult.

The code is built daily on a bunch of different platforms including multiple Linux distros, so the content in Git is good and should build. Try cloning the repo into a new directory and try again?
--
digital man (rob)

Rush quote #46:
One day I feel I'm on top of the world, and the next it's falling in on me Norco, CA WX: 71.3°F, 56.0% humidity, 6 mph WNW wind, 0.00 inches rain/24hrs

Hello Digital,

On Wed, 01 May 2024 13:51:42 -0700, you wrote to Dumas Walker:

The code is built daily on a bunch of different platforms including multiple Linux distros, so the content in Git is good and should build. Try cloning the repo into a new directory and try again?

If it's his production system, a 'make clean' may help as well.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- GoldED+/LNX 1.1.5-b20240309
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)