I've been having a hell of a time porting a standard linux/BSD program to OS-X and was wondering what some sources are online to get help with this kind of thing? 
I'm not sure if this forum is aimed towards technical discussions or not, but I've isolated a serious problem that my compiled project is running into and can't figure out why it's such a major hang up on OS-X, but works as intended on every other *nix variant.
My problem is namely this:
I have a function called mesg_parse(<tons of parameters>)
that parses a list style language. The nature of a list parser requires a lot of recursive calls to itself, so I have a macro that I use to simplify the process:
#define MesgParse(in, out) mesg_parse(<tons of parameters, including (in) and (out)>)
So mesg_parse() contains uses of the MesgParse macro to call itself recursively. While this works fine on BSD variants and linux, my program panics when it encounters lines with this macro on OS-X and I can't figure out why. Looking at debug traces, it would seem that the macro is being handled entirely wrong by the compilier.
I'm using OS-X 10.2,
and have tried compiling my project with both gcc2 and gcc3, using -no-cpp-precomp sometimes, and not other times, but all attempts to get this macro not to kill my program aren't working.
Does anyone have any suggestions I should check? Or any suggestions on forums where I could go with this kind of technical problem?
My project is
http://protomuck.sourceforge.net/
The file in question is:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/protomuck/protomuck/src/msgparse.c?rev=1.9
with the macro #def'd in inc/msgparse.h as:
#define MesgParse(in,out) mesg_parse(descr, player, what, perms, (in), (out), BUFFER_LEN, mesgtyp)
Any help with this or where I can go to get technical help with that kind of problem would be greatly appreciated!
-Akari
I'm not sure if this forum is aimed towards technical discussions or not, but I've isolated a serious problem that my compiled project is running into and can't figure out why it's such a major hang up on OS-X, but works as intended on every other *nix variant.
My problem is namely this:
I have a function called mesg_parse(<tons of parameters>)
that parses a list style language. The nature of a list parser requires a lot of recursive calls to itself, so I have a macro that I use to simplify the process:
#define MesgParse(in, out) mesg_parse(<tons of parameters, including (in) and (out)>)
So mesg_parse() contains uses of the MesgParse macro to call itself recursively. While this works fine on BSD variants and linux, my program panics when it encounters lines with this macro on OS-X and I can't figure out why. Looking at debug traces, it would seem that the macro is being handled entirely wrong by the compilier.
I'm using OS-X 10.2,
and have tried compiling my project with both gcc2 and gcc3, using -no-cpp-precomp sometimes, and not other times, but all attempts to get this macro not to kill my program aren't working.
Does anyone have any suggestions I should check? Or any suggestions on forums where I could go with this kind of technical problem?
My project is
http://protomuck.sourceforge.net/
The file in question is:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/protomuck/protomuck/src/msgparse.c?rev=1.9
with the macro #def'd in inc/msgparse.h as:
#define MesgParse(in,out) mesg_parse(descr, player, what, perms, (in), (out), BUFFER_LEN, mesgtyp)
Any help with this or where I can go to get technical help with that kind of problem would be greatly appreciated!
-Akari