From owner-freebsd-questions@FreeBSD.ORG Thu Jan 9 09:06:58 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 419B9A89 for ; Thu, 9 Jan 2014 09:06:58 +0000 (UTC) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by mx1.freebsd.org (Postfix) with ESMTP id CB6621DA2 for ; Thu, 9 Jan 2014 09:06:57 +0000 (UTC) Received: from ppp121-45-52-62.lns20.adl2.internode.on.net (HELO leader.local) ([121.45.52.62]) by ipmail05.adl6.internode.on.net with ESMTP; 09 Jan 2014 19:36:54 +1030 Message-ID: <52CE66AB.8050500@ShaneWare.Biz> Date: Thu, 09 Jan 2014 19:36:51 +1030 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: RW , freebsd-questions@freebsd.org Subject: Re: Can you switch from CLang back to gcc in FreeBSD 10.0 References: <52CDB91E.4060107@fjl.co.uk> <20140108225833.4088ee56@gumby.homeunix.com> <52CDE131.90804@fjl.co.uk> <20140109014652.04f208bc@gumby.homeunix.com> In-Reply-To: <20140109014652.04f208bc@gumby.homeunix.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 09:06:58 -0000 On 09/01/2014 12:16, RW wrote: > On Wed, 08 Jan 2014 23:37:21 +0000 > Frank Leonhardt wrote: > >> On 08/01/2014 22:58, RW wrote: >>> On Wed, 08 Jan 2014 20:46:22 +0000 >>> Frank Leonhardt wrote: >>> >>>> I've been dreading this for over a year now. >>> Any particular reason why you have to build the base system with >>> gcc? >>> >>>> It's going to reach >>>> critical soon. FreeBSD 10 is dropping gcc in favour of Clang >>> >>> I don't think that's quite true: >>> >>> >>> >>> >> >> As I understand it (and I haven't tried it, hence my question), all >> that does is build gcc along with the other stuff. It doesn't make >> gcc the default (only) compiler. Sean's editing of /etc/make.conf >> goes some way >> - or even hacking sys.mk. However, /usr/bin/cc wouldn't be linked to >> gcc for a start, > > > I think the canonical way of building world with gcc is to set > WITHOUT_CLANG_IS_CC (it's discussed in the thread I quoted) there's > also WITHOUT_CLANG. In 10.0 WITHOUT_GCC and WITH_CLANG_IS_CC are the default. You can buildworld using WITH_GCC and WITH_GCC_IS_CC and even WITHOUT_CLANG (man src.conf lists options) but consider the age of gcc v4.2.1 -(C)2007- that get's installed, it doesn't know what a corei7 is and it doesn't have the other bug fixes included with the later 4.2.x releases. If you want to use gcc I would suggest using gcc46 or gcc48 rather than gcc from base.