From owner-freebsd-ports Mon Nov 22 11:20:13 1999 Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 916CE1595D; Mon, 22 Nov 1999 11:19:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 647B31CD7BC; Mon, 22 Nov 1999 11:19:53 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 22 Nov 1999 11:19:53 -0800 (PST) From: Kris Kennaway To: Christian Weisgerber Cc: ports@freebsd.org Subject: Re: Flagging ports for "make -j"? In-Reply-To: <19991122171658.C17370@fettuccini.unix-ag.uni-kl.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 22 Nov 1999, Christian Weisgerber wrote: > I'm currently updating a string of ports on a dual-ppro box, and > I'm increasingly unhappy that some ports can be compiled with > "make -j", some can't, and there's no way to know unless you try. > > How about introducing a Makefile variable that tells whether a port > is j-safe? I guess we could add some Makefile juju to automatically > drop back to -j1 if parallel building is not supported. Satoshi's build cluster probably has some spare cycles on-hand for automated testing :-) OpenBSD have a build variable called NO_PARALLEL_BUILD or similar..I don't know if it controls the -j knob or parallel building between packages. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message