Error for external LibCalls while trying to compile old sources

6 posts / 0 new
Last post
Reth
Reth's picture
Offline
Last seen: 9 years 6 months ago
Joined: 2011-07-09 22:16
Error for external LibCalls while trying to compile old sources
Hi everybody, since I'm really uncommon in coding for AOS(4) and in internals I'm wondering what right solution would be when getting errors like these: header/AMarquee_protos.h:21: error: expected '=', ',', ';', 'asm' or '__attribute__' before '__regargs' Source of these problems are protos defined for that source (should be AMarquee.library of an older version when compile runs through): extern LibCall struct QSession * QNewSession(char * hostname, LONG port, char * progname);  /* returns socket descriptor */ Is the LibCall no longer appropriate here or do I have to provide some of the suggested prefixes above (or another one) or will sth. completely different help here? Many thanks in advance and Best Regards
thomas
thomas's picture
Offline
Last seen: 3 weeks 2 days ago
Joined: 2011-05-16 14:23
I am quite sure that
I am quite sure that "LibCall" (which seems to resolve to __regargs) is not an attribute known to GCC. Perhaps you should compile your program with GCC for 68k first to eliminate all those SASC-specifics. Or VBCC which is easier to install and use.
Reth
Reth's picture
Offline
Last seen: 9 years 6 months ago
Joined: 2011-07-09 22:16
Thanks thomas, what a pitty.
Thanks thomas, what a pitty. Hopefully I can try to compile on AOS3.9. Didn't do so for years now. Would VBCC of AOS4 also work (though I did not want to use that one at all)? Maybe somebody remembers these things from SASC and can tell a working way around (maybe I'll also ask in some other fora).
thomas
thomas's picture
Offline
Last seen: 3 weeks 2 days ago
Joined: 2011-05-16 14:23
VBCC is a great compiler. I
VBCC is a great compiler. I prefer it over every other solution. You can use OS4's VBCC to compile for 68k with the +aos68k switch. vc +aos68k program.c -o program For LibCall the solution is simply to remove it completely. Also remove everything beginning with __ like __asm or __stdargs for example.
Reth
Reth's picture
Offline
Last seen: 9 years 6 months ago
Joined: 2011-07-09 22:16
Never used VBCC since
Never used VBCC since personally I try to use C++. But the crosscompile option really sounds great! Regarding your statement referring to LibCall:
For LibCall the solution is simply to remove it completely. Also remove everything beginning with __ like __asm or __stdargs for example.
Does this refer to a general handling (i.e. can I do the same while using G++ of AOS4 - regarding your earlier post I'd suppose: No) or only when using VBCC?
kas1e
kas1e's picture
Offline
Last seen: 3 hours 53 min ago
Joined: 2010-11-30 15:30
@Reth You better start to use
@Reth You better start to use SDI macroses: they cover a lot of stuff, include all those SAVEDS, ASM, REG and co. Still some adaptation may need, but it worth of it (for example we use it to port dopus5, code of which full-blown-sasc-specific).
Log in or register to post comments