A dependency for $(EXTRANCITHUNKS_SO) is added. I hope that fix the problem.
-- Gerd Am Dienstag, den 22.02.2011, 04:15 +0100 schrieb Gerd Pokorra: > I am afraid you are right. I see that my vmware machine use only one CPU > and this fix the problem only for me but there seem to be a problem with > more CPUs. > I will look to add a dependency. Help is welcome. Should I switch back > in the meantime? > > -- Gerd > > Am Dienstag, den 22.02.2011, 04:02 +0100 schrieb Andy Dougherty: > > On Mon, 21 Feb 2011, Andy Dougherty wrote: > > > > > On Mon, 21 Feb 2011, Gerd Pokorra wrote: > > > > > > > Should already be fixed. > > > > > > > > -- Gerd > > > > > > > > Am Montag, den 21.02.2011, 20:05 +0100 schrieb Andy Dougherty: > > > > > As of RELEASE_3_1_0-210-g6786a80, the build fails for me with: > > > > > > My guess is that there is a dependency issue. Are you sure you updated > > > all the Makefile dependencies (including those in subdirectories) > > > appropriately? > > > > On a perhaps-related note, the following commit: > > > > commit 359f1d05fb932ea97e3675d0ec155c3e16134092 > > Author: Gerd Pokorra <g...@zimt.uni-siegen.de> > > Date: Mon Feb 21 14:16:41 2011 +0100 > > > > change the build order > > > > doesn't actually necessarily change the build order. In a Makefile rule > > such as > > > > all: a b c d > > > > there is no guarantee that a, b, c, and d will be built in that order. > > (In fact, I seem to recall that one of the BSD-derived makes actually > > has an option to deliberately scramble the order.) It so happens that > > GNU make -j 1 generally goes left-to-right, but that's an accident of > > implementation, not a rule. > > > > To force a particular order, the Makefile must have a proper > > dependency somewhere. I suspect that's what's missing here. > > > > > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev