1 Dec
2006
1 Dec
'06
10:57 p.m.
since the romcc builtin preprocessor silently eats lines of code, can we just use the gcc preprocessor (cpp) before calling romcc as a workaround?
That should work (if you get the -I directives, etc., right). But use gcc -E instead of cpp...
Is there a reason romcc has its own preprocessor?
Probably not.
Segher