I would serously think about trying gcc, vs Dec/Compaq/Whatever cc.
Gcc is pretty robust on VMS according to my rapidly failing VMS 
memory.

To generate interp.c

Interpreter translate: 'interp.c' doInlining: true.

This is from the class comment for CCodeGenerator

cheers

bruce


"Andrew C. Stoffel" <acs at campus.com> wrote:
> In my continuing attempt to evaluate my/the possibility
> of porting the Squeak VM to OpenVMS (I haven't decided yet
> if I'll attempt it though I DO know at this point that
> it won't be a simple recompile of the Unix Squeak+dealing
> with a completely different directory syntax. I'll still
> gathering information...)
> 
> I've run into a need to REALLY understand interp.c and
> how it's created/generated. (It gives all the version
> of the DEC/Compaq C compilers on OpenVMS that I've
> tried (including the most recent) SERIOUS heartburn
> (Details available upon request). I can either attempt
> to fix the 100+ functions in interp.c that are causing
> problems OR figure out how to generate an interp.c that
> doesn't exhibit these "problems"...
> 
> So I need some guidance/a path towards interp.c
> generation enlightenment & a search of the Squeak SWIKI
> only found me 2 mentions of interp.c.... but no "Hitchhikers Guide to 
> Interp.c" - maybe I'm looking for the wrong thing ?
> 
> Suggestions are welcome.....
> 
> Thanks.
> 
> -Andy-