From owner-cvs-ports@FreeBSD.ORG Wed Nov 16 07:41:51 2011 Return-Path: Delivered-To: cvs-ports@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 74BC81065675; Wed, 16 Nov 2011 07:41:51 +0000 (UTC) Date: Wed, 16 Nov 2011 07:41:51 +0000 From: Alexey Dokuchaev To: Ruslan Mahmatkhanov Message-ID: <20111116074151.GA4193@FreeBSD.org> References: <201111160321.pAG3LYf3033418@repoman.freebsd.org> <20111116044411.GA57332@FreeBSD.org> <4EC36744.6040204@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4EC36744.6040204@yandex.ru> User-Agent: Mutt/1.4.2.1i Cc: cvs-ports@FreeBSD.org, Eitan Adler , cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/lang/s9fes Makefile X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2011 07:41:51 -0000 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