From owner-freebsd-current@FreeBSD.ORG Fri Jun 11 19:25:46 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 796C9106567C for ; Fri, 11 Jun 2010 19:25:46 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 2A4478FC1D for ; Fri, 11 Jun 2010 19:25:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o5BJKlF9055151; Fri, 11 Jun 2010 13:20:47 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 11 Jun 2010 13:20:52 -0600 (MDT) Message-Id: <20100611.132052.271446115462387749.imp@bsdimp.com> To: ed@80386.nl From: "M. Warner Losh" In-Reply-To: <20100611185237.GL56080@hoeg.nl> References: <4C128548.8090505@fgznet.ch> <20100611185237.GL56080@hoeg.nl> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: andreast-list@fgznet.ch, freebsd-current@freebsd.org Subject: Re: How to disable CLANG & co build in buildworld? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2010 19:25:46 -0000 In message: <20100611185237.GL56080@hoeg.nl> Ed Schouten writes: : Hello Andreas, : : * Andreas Tobler wrote: : > I have a sparc64 machine which is quite slow. And for my purpose I : > do not need CLANG etc. atm. : : Clang is not enabled on sparc64, so there is no need to disable : anything. If you do want to disable Clang on i386, amd64, pc98 or : powerpc, add WITHOUT_CLANG=yes to /etc/src.conf, as described in : src.conf(5). Except that clang isn't quite disabled when cross-building, due to the issue I pointed out when the commit went in wrt bsd.own.mk. MACHINE_ARCH is still amd64 until we start to build the sparc64 binaries, so anything in the bootstrapping part of the build will not be disabled. that's one of many reasons disabling things in bsd.own.mk based on architecture is going to fail. Warner