On Tue, Jun 15, 2010 at 11:36 AM, Scott Webster <[email protected]> wrote: > use_parallel_build > This keyword is for specifying whether or not it is safe for a port to > use multiple CPUs or multiple cores in parallel during its build > phase. If use_parallel_build is not set to “no” in a given port, the > option -j${build.jobs} is passed to ${build.cmd} (if ${build.cmd} is > make or scons). > > Why would it pass -j${build.jobs} if use_parallel_build is set to NO? > Wouldn't you want to pass -j1 in this case, since by default > ${build.jobs} will be the number of cores (unless low memory)? > > Maybe this is just a typo and that "no" should be a "yes" or else I am > confused :)
Sigh, reading fail, it says NOT SET to "no" so everything is right with the world (why can't these things ever be seen before one hits "send"?). Nevermind. I assume that an equivalent way to workaround this problem would be to use: sudo port install manopen use_parallel_build=no Scott _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
