On 10/1/07, Gavin Maltby <[EMAIL PROTECTED]> wrote: > On 09/29/07 21:14, Patrick Ale wrote: > Do you have an aggressive DMAKE_MAX_JOBS (or setting for this > system in ~/.make.machines)? High parallelism is a good way to > exhaust memory on systems with limited memory, and it can take > only a modest increase in each compile job to amount to enough > to exhaust the system. Try tuning back to 4 or less and see > if the compile succeeds without running out of resource.
Hi, I don't have a ~/.make.machines file. When I look in the opensolaris.sh environmental file I see there is some calculation done, CPUs + 2 or something (which comes to 4 in my case). I think I fixed it though, outcome is I really needed more swap.. I BFU-ed to the debug archives of b73 (downloaded from the /on/downloads/ site) and tried to recompile onnv_74, same /tmp full errors, which kinda ruled out a problem with onnv_74 itself. So, compiling any onnv_gate on SXCE72 works, compiling onnv_73 and onnv_74 on b73-debug and onnv_74 debug does not work with 512MB of swap. When I repartitioned my disk and defined a 2GB slice for swap, iI was capable of compiling onnv_74 under a debug-enabled host (in this case b73) Could it be that a system with 'debug' enabled makes me hit some heavy swap or /tmp usage during compilation that I don't notice when compiling on a non-debug host? And if yes, is there a recommended value for swap or /tmp when you compile debug enabled onnv-gates? Obviously 2GB of RAM isnt enough, at least not in my case. Anyway, I am going to retry what happens with Sun Studio 12 now as well, should be fun :) I hope this wasn't a waste of your time, and if it was, sorry for that. Patrick _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
