From owner-freebsd-toolchain@freebsd.org Mon Mar 14 04:21:10 2016 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67649AD0392 for ; Mon, 14 Mar 2016 04:21:10 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4498562F for ; Mon, 14 Mar 2016 04:21:09 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id u2E4Kt1f070185; Sun, 13 Mar 2016 21:21:02 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: Warner Losh Cc: FreeBSD toolchain In-Reply-To: References: <779997a4a2f241b39db096bfed5cb84f@ultimatedns.net>, From: "Chris H" Subject: Re: How to insist on only clang, for world/kernel? Date: Sun, 13 Mar 2016 21:21:02 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8a1bef70c8957e7f05eeef4d2d88703a@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Mar 2016 04:21:10 -0000 On Sun, 13 Mar 2016 17:32:55 -0600 Warner Losh wrote > Then you may be able to do make buildworld CC=clang (or whatever clang is > compiled as. > No guarantee, sine I've not played with 9.x in a while. > > Warner Apologies. Appears my response wasn't clear. I had no difficulties getting clang (and only clang) by placing your suggestions in src.conf(5). Whereas prior to those, I got gcc as cc. Thanks again, Warner. > > > On Fri, Mar 11, 2016 at 8:20 AM, Chris H wrote: > > > On Thu, 10 Mar 2016 21:49:01 -0700 Warner Losh wrote > > > > > make buildworld WITH_CLANG=t WITH_CLANG_BOOTSTRAP=t WITHOUT_GCC=y > > > WITHOUT_GCC_BOOTSTRAP=t WITH_CLANG_IS_CC=t > > > make buildkernel > > > > > > But that's mostly default these days, so really most people get what you > > > want by doing > > > > > > make buildworld buildkernel > > > > > > Warner > > Thanks for the quick reply, Warner! > > This is on RELENG_9, so I *don't* get that by default. ;) > > But true. Everything else I run in on -CURRENT, and indeed gets > > the options you indicate above out-of-the-box. > > > > Thanks again, Warner. > > > > > > On Thu, Mar 10, 2016 at 9:23 PM, Chris H wrote: > > > > > > > Greetings, > > > > A recent build/install world/kernel on a fresh 9-STABLE. > > > > I was surprised to see that, while clang was also built, > > > > gcc was used to perform the build for at least world. > > > > I performed some research to definitively determine the > > > > magic incantation for at least src.conf(5). However, I > > > > found too many possibilities to be sure. So I'm here > > > > to beg for the answer. > > > > > > > > The most likely candidates I have so far > > > > > > > > FAVORITE_COMPILER=clang > > > > MAKE_COMPILER_TYPE=clang > > > > WITH_CLANG=true > > > > CC=clang > > > > CXX=clang++ > > > > CPP=clang-cpp > > > > > > > > Thanks you. > > > > > > > > --Chris > > > > -- > > > > > > --Chris --