Date: Tue, 20 Sep 2011 23:20:36 -0400 From: "b. f." <bf1783@googlemail.com> To: h h <aakuusta@gmail.com> Cc: cvs-ports@freebsd.org, ports-committers@freebsd.org, cvs-all@freebsd.org, Brendan Fabeny <bf@freebsd.org> Subject: Re: cvs commit: ports/security/tor Makefile Message-ID: <CAGFTUwOK%2BSYPsoxec%2BfpKtJcjO67cv481AqRvpoPfwxtmC6DjQ@mail.gmail.com> In-Reply-To: <86ehzbhhv0.fsf@gmail.com> References: <201109200133.p8K1X0r8029934@repoman.freebsd.org> <86ehzbhhv0.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/20/11, h h <aakuusta@gmail.com> wrote: > Brendan Fabeny <bf@FreeBSD.org> writes: > >> bf 2011-09-20 01:33:00 UTC >> >> FreeBSD ports repository >> >> Modified files: >> security/tor Makefile >> Log: >> add a few mirrors and mark MAKE_JOBS_UNSAFE [1] > > Why not mark port as USE_GMAKE? GNU automake rarely generates makefiles > conforming to BSD make rather than GNU make. And it builds fine with > -j16 when using gmake. > I'm not sure what you're referring to here. The autotools make an attempt to be portable to many different environments, and quite often succeed. Of course, this also depends on the work of those using autotools. There are some issues, like those discussed in the autoconf manual, and some of those are related to the way that parallelism is handled in different make implementations. But I would prefer to avoid adding a dependency on devel/gmake. Maybe you have looked into this, and found the particular Makefile constructs that are preventing parallel builds with the system make in this instance? b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGFTUwOK%2BSYPsoxec%2BfpKtJcjO67cv481AqRvpoPfwxtmC6DjQ>