-j2 default and sudo usage

Anil Madhavapeddy anil at recoil.org
Fri Jul 31 07:52:50 PDT 2009

That works great; I've left my global setting at the default 0.
The problem with leaving this the release default is that lots of
my ports (but I bet others too) fail silently if using recursive
sub-makes and only install a partial collection of files and a
broken port.  I'll submit tickets to mark my relevant ports correctly
as single-build only.


On Thu, Jul 30, 2009 at 07:52:20PM -0700, Toby Peterson wrote:
> If you run across ports that don't build in parallel, they should have 
> "use_parallel_build no" set. If you don't want to bother modifying (and 
> reporting) those ports, you can set "buildmakejobs 1" in macports.conf
> - Toby
> On Jul 30, 2009, at 7:39 AM, Anil Madhavapeddy wrote:
>> Couple of questions:
>> Just installed the svn macports, and ports seem to build with -j2 now by 
>> default.  Is this a recent change, since loads of OCaml ports break with a 
>> parallel build.  Should I go around setting each individual port to have a 
>> -j1 in the Portfile, or is there some other way to force a non-parallel 
>> build with a variable?
>> Also, how do folks typically do non-root builds to ensure stuff isn't 
>> sneaking out of the fakeroot? I've chowned a bunch of directories to my 
>> user, and manually invoking fakeroot works; it would be nice if sudo were 
>> automatically called when required (e.g. for install).  Is there a knob 
>> for this, or do you generally just invoke targets manually and add sudo 
>> when required?
>> -anil
>> _______________________________________________
>> macports-dev mailing list
>> macports-dev at lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Anil Madhavapeddy                                 http://anil.recoil.org

More information about the macports-dev mailing list