| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | re: undefined symbol _Rxframeind & _Rxtype |
I am pretty sure that all of the final Max 3.x builds were done under OS/2, so your mileage with Win XP may vary. The "_" prefix comes from the standard convention used by WATCOM C: variables with external scope automatically have a "_" prefix added. In other words, don't worry about it. I don't recall exactly which version of the source is out there, but the last one I have at my disposal has Rxframeind and Rxtype both defined and used in prot/zm.c. I don't know if I still even have my WC discs lying around anymore, so I am not at liberty to try compilation...but if I had to hazard a guess, I'd say that there appear to be conflicting declarations for those two variables. In ZM.H,the declaration is "extern Rxframeind", whereas it is "static int Rxframeind" in ZM.C. "extern" implies the opposite of "static", so maybe if you delete the lines containing the extern references for those variables in zmodem.h and zsjd.h, the compiler may be happy. Just keep in mind that I haven't looked at this code in a very long time, so take that advice for what it's worth! Scott --- Maximus/2 2.02* Origin: -=( The TechnoDrome )=- (1:382/61) SEEN-BY: 10/1 11/200 201 203 331 34/999 120/228 123/500 128/2 187 140/1 222/2 SEEN-BY: 226/0 236/150 249/303 250/1 306 261/20 38 100 1404 1406 1418 266/1413 SEEN-BY: 280/1027 320/119 393/11 396/45 633/104 260 267 640/954 690/682 734 SEEN-BY: 712/0 313 848 800/432 801/161 189 2222/700 2320/100 5030/1256 @PATH: 382/61 140/1 261/38 633/260 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.