From owner-freebsd-current@FreeBSD.ORG Mon Sep 9 13:38:00 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0D3812E1; Mon, 9 Sep 2013 13:38:00 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D0F8025E5; Mon, 9 Sep 2013 13:37:59 +0000 (UTC) Received: from c120.sec.cl.cam.ac.uk (c120.sec.cl.cam.ac.uk [128.232.18.120]) (authenticated bits=0) by theravensnest.org (8.14.5/8.14.5) with ESMTP id r89Dbq9d097032 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 9 Sep 2013 13:37:53 GMT (envelope-from theraven@FreeBSD.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: HEADS UP: No gcc by default in -HEAD on platforms where clang is cc From: David Chisnall In-Reply-To: <20130909132758.GK9030@acme.spoerlein.net> Date: Mon, 9 Sep 2013 14:37:51 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <23F19F73-738E-4490-BAE3-590C32FC141C@FreeBSD.org> <20130909132758.GK9030@acme.spoerlein.net> To: =?iso-8859-1?Q?Ulrich_Sp=F6rlein?= X-Mailer: Apple Mail (2.1508) Cc: freebsd-current CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 09 Sep 2013 13:38:00 -0000 On 9 Sep 2013, at 14:27, Ulrich Sp=F6rlein wrote: > Case in point, I only recently switched to clang in base and now the > newsbeuter port crashes during startup (yeah, it builds fine). So all > I'm asking for now is: how can I override a random port to be built = with > gcc (either from base or ports, I don't care). And what special > considerations need to be done when the port uses C++. Setting USE_GCC=3Dany to build with any gcc, or USE_GCC=3Dyes to build = with a gcc from ports (they should do the same thing on a no-gcc-in-base = system) For C++ ports, can you check whether the error is from libc++ or clang, = by first building libstdc++ from base and then setting = CXXFLAGS=3D-stdlib=3Dlibstdc++ and LDFLAGS=3D-stdlib=3Dlibstdc++? This = will build it with libstdc++ and if that works then it narrows the issue = down. =20 Also, don't forget to report bugs to the port maintainer... David