Date: Wed, 16 Nov 2011 07:41:51 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Ruslan Mahmatkhanov <cvs-src@yandex.ru> Cc: cvs-ports@FreeBSD.org, Eitan Adler <eadler@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/s9fes Makefile Message-ID: <20111116074151.GA4193@FreeBSD.org> In-Reply-To: <4EC36744.6040204@yandex.ru> References: <201111160321.pAG3LYf3033418@repoman.freebsd.org> <20111116044411.GA57332@FreeBSD.org> <4EC36744.6040204@yandex.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 16, 2011 at 11:33:24AM +0400, Ruslan Mahmatkhanov wrote: > Alexey Dokuchaev wrote on 16.11.2011 08:44: > > Oh come on. Why blindly mark ports as -jX unsafe when trivial fix is > > discoverable in a minute? > > By the way, how one can detect that some port is jobs unsafe? Can this > be detected on single CPU machine? It depends. Sometimes it can, sometimes the build only woes on something four cored in certain phase of moon. This particular port was easy as it exhibited the problem (due to missing make target prerequisite) even on my single CPU laptop. Usually trying to build the port like this is a good start: make FORCE_MAKE_JOBS=y MAKE_JOBS_NUMBER=2 (sometimes 3, 4, or 42 might work better) ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111116074151.GA4193>