On Fri, 21 Nov 2003, Harry wrote: > --- Dan Sugalski <[EMAIL PROTECTED]> wrote: > > Should be straightforward though it involves diving into a twisty > > maze of > > make rules, so maybe not. Anyway, trying a "make -j 4" dies a quick > > and > > horrible death, failing to find Parrot/OpLib/core.pm. My assumption > > here > > is that we're just missing some dependency rules, as a make -j 2, or > > a > > make -j 4 after a failed make -j 4 works just fine. > > I am having a quick look at it now. I copied the Parrot/OpLib/core.pm > to a backup file, did a make clean, which removes the file. I then > copied it back to its normal position and ran "make -j 4" and it worked > a treat so I am now trying to see at which point in the process the > file gets created because it appears to be created a bit too late for > "make" to work. (Maybe this is what you where getting at above).
I was mostly thinking that some step or other in the Makefile has a dependency on that file, and some other step creates it, but the dependency's not explicit. I'd like to find the step(s) that require it and make it a dependency for them, then add in a dependency for the file for whatever step actually creates it, so things get ordered properly. It should (hopefully) be straightforward, but... Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk