From owner-freebsd-ports Mon Nov 22 8:17:28 1999 Delivered-To: freebsd-ports@freebsd.org Received: from news.uni-kl.de (news.uni-kl.de [131.246.137.51]) by hub.freebsd.org (Postfix) with SMTP id 3676414CE9 for ; Mon, 22 Nov 1999 08:17:14 -0800 (PST) (envelope-from naddy@unix-ag.uni-kl.de) Received: from sushi.unix-ag.uni-kl.de ( root@sushi.unix-ag.uni-kl.de [131.246.89.13] ) by news.uni-kl.de id aa11530 for ; 22 Nov 1999 17:19 MEZ Received: from fettuccini.unix-ag.uni-kl.de (fettuccini.unix-ag.uni-kl.de [131.246.89.27]) by sushi.unix-ag.uni-kl.de (8.9.3/8.9.1) with ESMTP id RAA32398 for ; Mon, 22 Nov 1999 17:16:52 +0100 Received: (from naddy@localhost) by fettuccini.unix-ag.uni-kl.de (8.9.3/8.9.3) id RAA31088 for ports@freebsd.org; Mon, 22 Nov 1999 17:16:59 +0100 (CET) (envelope-from naddy) Date: Mon, 22 Nov 1999 17:16:58 +0100 From: Christian Weisgerber To: ports@freebsd.org Subject: Flagging ports for "make -j"? Message-ID: <19991122171658.C17370@fettuccini.unix-ag.uni-kl.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. Opinions on the general idea? -- Christian "naddy" Weisgerber naddy@unix-ag.uni-kl.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message