I think I finally figured out what the problem was with the classes/ makefile, that caused strange things to happen. :)
Patch included below. Should the various files also depend upon pmc2c.pl, so they will be regenerated in the event of a change to the generator? Or is that going too far? Technically, all of the .ops generation code would also need to be a dependancy for the core_ops*.c files themselves. Mike Lambert Index: classes/Makefile.in =================================================================== RCS file: /cvs/public/parrot/classes/Makefile.in,v retrieving revision 1.19 diff -u -r1.19 Makefile.in --- classes/Makefile.in 29 Jan 2002 04:26:21 -0000 1.19 +++ classes/Makefile.in 20 May 2002 00:37:39 -0000 @@ -26,7 +26,7 @@ all : $(O_FILES) -array.c array.h: array.pmc +array.c array.h: array.pmc default.pmc $(PMC2C) array.pmc array$(O): $(H_FILES) @@ -36,42 +36,42 @@ default$(O): $(H_FILES) -perlint.c perlint.h: perlint.pmc +perlint.c perlint.h: perlint.pmc default.pmc $(PMC2C) perlint.pmc perlint$(O): $(H_FILES) -perlnum.c perlnum.h: perlnum.pmc +perlnum.c perlnum.h: perlnum.pmc default.pmc $(PMC2C) perlnum.pmc perlnum$(O): $(H_FILES) -perlstring.c perlstring.h: perlstring.pmc +perlstring.c perlstring.h: perlstring.pmc default.pmc $(PMC2C) perlstring.pmc perlstring$(O): $(H_FILES) -perlarray.c perlarray.h: perlarray.pmc +perlarray.c perlarray.h: perlarray.pmc default.pmc $(PMC2C) perlarray.pmc perlarray$(O): $(H_FILES) -perlhash.c perlhash.h: perlhash.pmc +perlhash.c perlhash.h: perlhash.pmc default.pmc $(PMC2C) perlhash.pmc perlhash$(O): $(H_FILES) -perlundef.c perlundef.h: perlundef.pmc +perlundef.c perlundef.h: perlundef.pmc default.pmc $(PMC2C) perlundef.pmc perlundef$(O): $(H_FILES) -parrotpointer.c: parrotpointer.pmc +parrotpointer.c parrotpointer.h: parrotpointer.pmc default.pmc $(PMC2C) parrotpointer.pmc parrotpointer$(O): $(H_FILES) -intqueue.c: intqueue.pmc +intqueue.c intqueue.h: intqueue.pmc default.pmc $(PERL) pmc2c.pl intqueue.pmc intqueue$(O): $(H_FILES)