when sbbsehco creates a .pkt file. Is there a way to tell which node it is intended for? Trying to help Terry out, he's got a bunch of packets in outgoing such as 4c967bf1.pkt 4c967bf2.pkt etc but they should be in each nodes outgoing dir. I can move them for him, but I need to figure which go where.
Use pktdump or a similar utility to view the packet headers and that will tell you the destination address of each packet file.
Re: Figure which pkt goes to which node?
By: Digital Man to Nelgin on Thu Sep 06 2018 06:21 pm
Use pktdump or a similar utility to view the packet headers and that will tell you the destination address of each packet file.
Is pktdump and msgdump supposed to be in my exec directory? They are not.
How would someone go about compiling those two programs?
Compiling for *nix, would be like:
gcc -DHAS_INTTYPES_H=1 -I../xpdev pktdump.c -o pktdump
Re: Figure which pkt goes to which node?
By: Digital Man to Al on Fri Sep 07 2018 01:34 am
Compiling for *nix, would be like:
gcc -DHAS_INTTYPES_H=1 -I../xpdev pktdump.c -o pktdump
When I run that command I get..
In file included from fidodefs.h:39:0,
from pktdump.c:5:
../xpdev/gen_defs.h:165:17: error: conflicting types for rCyint8_trCO
typedef char int8_t;
^
In file included from ../xpdev/gen_defs.h:62:0,
from fidodefs.h:39,
from pktdump.c:5:
/usr/include/sys/types.h:194:1: note: previous declaration of rCyint8_trCO was here
__intN_t (8, __QI__);
^
In file included from fidodefs.h:39:0,
from pktdump.c:5:
../xpdev/gen_defs.h:167:17: error: conflicting types for rCyint32_trCO
typedef long int32_t;
^
In file included from ../xpdev/gen_defs.h:62:0,
from fidodefs.h:39,
from pktdump.c:5:
/usr/include/sys/types.h:196:1: note: previous declaration of rCyint32_trCO was
here
__intN_t (32, __SI__);
^
In file included from fidodefs.h:39:0,
from pktdump.c:5:
../xpdev/gen_defs.h:179:30: error: conflicting types for rCyint64_trCO
typedef signed long long int int64_t;
^
In file included from ../xpdev/gen_defs.h:62:0,
from fidodefs.h:39,
from pktdump.c:5:
/usr/include/sys/types.h:197:1: note: previous declaration of rCyint64_trCO was
here
__intN_t (64, __DI__);
^
Is there something more I need to do?
It worked for me. Maybe you mis-copy/pasted the command? Double-check the spelling of '-DHAS_INTTYPES_H=1'. If you're using a really old version of gcc, then you would need to remove that part, but I doubt you are.
Re: Figure which pkt goes to which node?
By: Digital Man to Al on Fri Sep 07 2018 11:19 am
It worked for me. Maybe you mis-copy/pasted the command? Double-check the
spelling of '-DHAS_INTTYPES_H=1'. If you're using a really old version of
gcc, then you would need to remove that part, but I doubt you are.
My slackware has gcc 5.5.0. I get the same result with or without -DHAS_INTTYPES_H=1.
Re: Figure which pkt goes to which node?
By: Digital Man to Al on Fri Sep 07 2018 11:19 am
It worked for me. Maybe you mis-copy/pasted the command? Double-check the spelling of '-DHAS_INTTYPES_H=1'. If you're using a really old version of gcc, then you would need to remove that part, but I doubt you are.
My slackware has gcc 5.5.0. I get the same result with or without -DHAS_INTTYPES_H=1.
I just wane into /sbbs/src/sbbs3 and did make msgdump and a make pkgdump then moved the two binaries into the exec directory.
You may get some warnings. Obviously all this gones onto one line.
My slackware has gcc 5.5.0. I get the same result with or without
-DHAS_INTTYPES_H=1.
That's pretty weird. Actually, sort of impossible. :-)
I builds error/warning free when I did as Nelgin suggested.. :)
Nothing is impossible, here at The Rusty MailBox!
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495939:39:55 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 286,971 |