Date: Wed, 16 Nov 2011 11:47:44 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: Alexey Dokuchaev <danfe@FreeBSD.org> 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: <4EC36AA0.7000302@yandex.ru> In-Reply-To: <20111116074151.GA4193@FreeBSD.org> References: <201111160321.pAG3LYf3033418@repoman.freebsd.org> <20111116044411.GA57332@FreeBSD.org> <4EC36744.6040204@yandex.ru> <20111116074151.GA4193@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Dokuchaev wrote on 16.11.2011 11:41: > 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 Thanks. -- Regards, Ruslan Tinderboxing kills... the drives.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC36AA0.7000302>