From owner-freebsd-ports@FreeBSD.ORG Tue Mar 24 13:34:01 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84A65106564A for ; Tue, 24 Mar 2009 13:34:01 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from raven.customer.vol.cz (raven.customer.vol.cz [195.250.144.108]) by mx1.freebsd.org (Postfix) with ESMTP id EB90B8FC0C for ; Tue, 24 Mar 2009 13:34:00 +0000 (UTC) (envelope-from pav@FreeBSD.org) Received: from [172.19.10.16] (nat-application.b1.lan.prg.vol.cz [195.122.204.152]) (authenticated bits=0) by raven.customer.vol.cz (8.14.3/8.14.3) with ESMTP id n2ODXrjU098320 for ; Tue, 24 Mar 2009 14:33:54 +0100 (CET) (envelope-from pav@FreeBSD.org) From: Pav Lucistnik To: ports@FreeBSD.org Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-kZGyG/rgO72LWnSAs+YD" Date: Tue, 24 Mar 2009 14:33:52 +0100 Message-Id: <1237901632.1849.19.camel@pav.hide.vol.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 FreeBSD GNOME Team Port X-Spam-Score: -1.933 () AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.64 on 195.250.144.108 X-Milter: Spamilter (Reciever: raven.customer.vol.cz; Sender-ip: 195.122.204.152; Sender-helo: [172.19.10.16]; ) Cc: Subject: HEADS UP multi processor compilations for everyone X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pav@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 13:34:01 -0000 --=-kZGyG/rgO72LWnSAs+YD Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Two days ago, I have checked in probably most requested feature of last few years. Ports framework now systematically supports building ports on multiple processing cores. It is achieved by passing -jX flag to make(1) running on vendor code. Of course not all ports handle this well, experimental run on pointyhat with this flag globally enabled turned up shy of 400 failures. Because of that, the feature was designed as a whitelist. Individual ports need to be enabled, and indeed, fellow developers took on and already started adding required declarations to popular ports like Firefox and others. If you are FreeBSD ports user: You don't need to do anything to enable the new feature. Whitelisted ports will automatically make use of all processors available in your computer. If you want, for some reasons, to disable this feature, put DISABLE_MAKE_JOBS=3Dyes to your /etc/make.conf. By default, the level of parallelization will be equal to a number of processing cores in your machine. If you want to override this number, use for example MAKE_JOBS_NUMBER=3D6, again in /etc/make.conf. And if you are extra brave, or you want to check out all the yet unmarked ports, if they will build, you can define FORCE_MAKE_JOBS=3Dyes in /etc/make.conf. If you are FreeBSD port maintainer: Nothing changes for you, if you don't want. If you want to enable the use of multiple cores in your port, add MAKE_JOBS_SAFE=3Dyes to a block somewhere below dependency declarations. If you know your port does not handle -jX well, and want to disable it from using -jX even when user forces this feature, use MAKE_JOBS_UNSAFE=3Dyes. And that's all to it. --=20 Pav Lucistnik What do we know about love? Love is like a pear. Pear is sweet and have a specific shape. Try to exactly define the shape of a pear. -- Marigold: 50 Years Of Poetry --=-kZGyG/rgO72LWnSAs+YD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAknI4UAACgkQntdYP8FOsoJ0dACgqpz7upUOMBta9ldTpAgBpsdR SEoAn1Bgf1BnXx1og5GlqBr0ul9dhrhb =0vpY -----END PGP SIGNATURE----- --=-kZGyG/rgO72LWnSAs+YD--