Now, this is interesting...If I type "jam -q haiku-image", it spews and quits in about 1 second, with the same stuff as before.
If I type "jam -a -q haiku-image", it does the exact same thing.If I type "jam haiku-image", it skips a bunch of stuff, but it continues on doing the things it can. If I type "jam -a haiku-image", it skips over a TON of things, but continues on things it can.
The -q parameter seems to be causing/invoking the problem. But why? And why is Jam skipping stuff now? In every incident where it started skipping stuff, it ended up never finishing the JAM and the Haiku image was never done. Is "skipping..." now acceptable or will I likely see the same result and no image of Haiku in the end?
Should I just try deleting the whole /trunk directory and starting over? Luposian