app-emulation/mol produces non-determinant errors when compiling with MAKEOPTS='-j2' (or higher, I would assume). Overriding with an empty MAKEOPTS variable fixes the problem. Reproducible: Always Steps to Reproduce: 1. MAKEOPTS='-j2' emerge app-emulation/mol Actual Results: Compilation will usually error out, though at different places, often complaining that it couldn't create a temporary directory because it already exists. It seems to be assuming that each make step completes before another one begins, meaning it is incompatible with anything higher than -j1. Expected Results: Not every Makefile is parallel make compatible, so the error is not unexpected. However, the -j switch to make should probably be overridden in the ebuild for mol.
I had never problems with -j2 (only the output looks a little bit "damaged") on my iBook 600. Which kind of CPU do you have?
Sorry, I should have mentioned that w/ the initial report. I have a PPC 7410 (500 MHz G4) in a first-generation TiBook.
I encountered the same problem on a dual 1.25GHZ system. Mol had compiled several times before, but wouldn't work over the past few days, with the following error: ok ok + Entering drivers Compiling driver_mgr.o : mkdir: cannot create directory `.objs-ppc': File exists make[2]: *** [.objs-ppc/.dummy] Error 1 make[2]: *** Waiting for unfinished jobs.... + Entering disk make[2]: *** Waiting for unfinished jobs.... Compiling blkdev.o : Compiling disk_open.o : make[2]: *** Waiting for un ok Compiling ablk.o : ok Compiling pseudofs.o : ok Compiling scsi.o : ok Compiling scsidev.o : ok Compiling ablk-cd.o : ok ok ok make[1]: *** [sub-drivers-all] Error 2 make: *** [sub-src-all] Error 2 !!! ERROR: app-emulation/mol-0.9.70 failed. !!! Function src_compile, Line 67, Exitcode 2 !!! Build mol with: FEATURES="-userpriv -strict" emerge mol Running FEATURES="-userpriv -strict" MAKEOPTS="" emerge mol fixed me right up.
fixed in cvs
