Date: Fri, 20 Sep 2013 14:32:35 -0400 From: Thomas Laus <lausts@acm.org> To: Gary Palmer <gpalmer@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: FreeBSD 9-Stable + Atom D510 Freeze Message-ID: <20130920183235.GA50866@mail.laus.org> In-Reply-To: <20130920155208.GA55143@in-addr.com> References: <523AFF46.29244.4657A1@lausts.acm.org> <523B91F2.8070004@heuristicsystems.com.au> <523C49A9.5719.289C1E@lausts.acm.org> <20130920143615.GA40029@in-addr.com> <20130920144928.GA50355@mail.laus.org> <20130920155208.GA55143@in-addr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Palmer [gpalmer@freebsd.org] wrote: > It's not a compiler flag, it's a make flag. make -j n will fork off up to > n compilers to do the build. If you just do "make buildworld" then there > is no parallel compilation. > > It used to be that ports had MAKE_JOBS_SAFE in the Makefile to mark that > the port could be built using parallel compiles with the '-j' argument > to make. It appears that the logic has been switched and now you have > to mark them as MAKE_JOBS_UNSAFE to say that parallel builds shouldn't be > done, indicating that parallel builds are the default now (unless I'm > misreading the code) > > You can try putting > > DISABLE_MAKE_JOBS=yes > > into /etc/make.conf to see if that stops the problem on port builds. > Gary: I don't see that as an option in /usr/share/examples/etc/make.conf. Did you find that one by reading the source code? I will add that to my /etc/make.conf and see if it makes a difference. This issue is very intermittant and may not trigger for weeks or months. I'll repost to the list if any problems show up after setting the flag in my /etc/make.conf Thanks for the help. Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130920183235.GA50866>