From owner-freebsd-arch@FreeBSD.ORG Tue Jul 8 17:37:06 2014 Return-Path: Delivered-To: freebsd-arch@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 ESMTPS id 82A4FECA; Tue, 8 Jul 2014 17:37:06 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "tensor.andric.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AB2C2CA9; Tue, 8 Jul 2014 17:37:05 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::1133:f181:93e3:e668] (unknown [IPv6:2001:7b8:3a7:0:1133:f181:93e3:e668]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 0AF795C44; Tue, 8 Jul 2014 19:37:01 +0200 (CEST) Content-Type: multipart/signed; boundary="Apple-Mail=_CA779C27-4913-4607-9D9A-2F4D1800CFF6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Total confusion over toolchain/xdev behavior From: Dimitry Andric In-Reply-To: Date: Tue, 8 Jul 2014 19:36:48 +0200 Message-Id: References: <1404688077.1059.115.camel@bruno> <1404766292.65432.43.camel@revolution.hippie.lan> <20B72004-1499-4F99-A7C7-13173C50C7C6@bsdimp.com> <20140707235237.GG97203@ivaldir.etoilebsd.net> <67272C53-1908-454A-8E74-14D9A2EA0828@FreeBSD.org> To: Warner Losh X-Mailer: Apple Mail (2.1878.6) Cc: Baptiste Daroussin , sbruno@FreeBSD.org, Ian Lepore , freebsd-arch@FreeBSD.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jul 2014 17:37:06 -0000 --Apple-Mail=_CA779C27-4913-4607-9D9A-2F4D1800CFF6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 08 Jul 2014, at 18:23, Warner Losh wrote: >=20 > On Jul 8, 2014, at 9:04 AM, Warner Losh wrote: >=20 >>=20 >> On Jul 8, 2014, at 12:56 AM, Dimitry Andric wrote: >>=20 >>> On 08 Jul 2014, at 03:56, Warner Losh wrote: >>>=20 >>>>=20 >>>> On Jul 7, 2014, at 7:29 PM, Warner Losh wrote: >>>>>=20 >>>>> About the rest=85 Yea, you may be right=85. MK_GNUCXX is an odd = duck, and that=92s >>>>> likely the problem that should be fixed in a different way. It is = really an internal >>>>> variable that should be set based on the actual compiler type = (possibly with an >>>>> override for the odd-duck pair of clang and libstdc++ which may = not be worth >>>>> supporting). It is telling us we=92re doing something horribly = wrong and we should listen >>>>> to that rather than add another compiler-related kludge to the = build system. I=92ll work >>>>> on that bit. >>>>=20 >>>> Perhaps >>>> http://people.freesbd.org/~imp/patch-queue/86gnucxx >>>> might be the best way to cope=85 >>>>=20 >>>> Comments? >>>=20 >>> This would make it impossible to build libstdc++ with clang, and why = remove MK_GNUCXX at all[1]? >>=20 >> Because it is a silly option that=92s mostly an internal knob? We = don=92t need to support options that trip us up at every turn, and = MK_GNUCXX has been doing that since its introduction. >=20 > Also, in the current tree it means different things in different = places. In some places it says to build libstdc++, in other places it = says to build g++ and friends. This was an oddity introduced by theraven@ in r255321, where he = introduced MK_GNUCXX, but I have no idea why he conflated the two. = Before this commit, I had a local patch which simply added an option = disabling or enabling libstdc++ and libsupc++ (and nothing else). I = should have committed that first... :) In any case, it would be nice to still have the option to enable = building libstdc++, whatever the used compiler is. -Dimitry --Apple-Mail=_CA779C27-4913-4607-9D9A-2F4D1800CFF6 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) iEYEARECAAYFAlO8LDcACgkQsF6jCi4glqNInQCfYZrYReFzJL/ORfNtyu9jN2uW YEoAnidn+G/GSflB3eNcOtCWxiQMEG9T =TOYl -----END PGP SIGNATURE----- --Apple-Mail=_CA779C27-4913-4607-9D9A-2F4D1800CFF6--