From owner-freebsd-toolchain@freebsd.org Sun Nov 5 01:02:20 2017 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 3E17BE5C4F7 for ; Sun, 5 Nov 2017 01:02:20 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-164.reflexion.net [208.70.210.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFF6F66489 for ; Sun, 5 Nov 2017 01:02:19 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 32227 invoked from network); 5 Nov 2017 01:02:18 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 5 Nov 2017 01:02:18 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Sat, 04 Nov 2017 21:02:18 -0400 (EDT) Received: (qmail 4639 invoked from network); 5 Nov 2017 01:02:18 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 5 Nov 2017 01:02:18 -0000 Received: from [192.168.1.25] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id 60655EC7B31; Sat, 4 Nov 2017 18:02:17 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: [toolchain] lib/clan/llvm.build.mk: Shouldn't BUILD_TRIPLE definition rely host 'cc -dumpmachine'? From: Mark Millard In-Reply-To: Date: Sat, 4 Nov 2017 18:02:16 -0700 Cc: Gerald Pfeifer , freebsd-arm@freebsd.org, freebsd-toolchain@freebsd.org, Dimitry Andric Content-Transfer-Encoding: quoted-printable Message-Id: <12E66105-6E1D-4941-B4C4-3BBAC0F3B330@dsl-only.net> References: <7CAFD8CC-BDA1-4E89-BD7E-D0089E27036F@dsl-only.net> To: =?utf-8?Q?Eddy_Petri=C8=99or?= X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Nov 2017 01:02:20 -0000 On 2017-Nov-4, at 5:19 PM, Eddy Petri=C8=99or wrote: > Pe 5 nov. 2017 12:57 AM, "Gerald Pfeifer" a = scris: > On Sun, 29 Oct 2017, Eddy Petri=C8=99or wrote: > > Yep --and it is even more complicated: gcc vs. clang are sometimes > > different for the target listed. . . > > > > For example -m32 for amd64 changes the clang result: > > > > # clang -dumpmachine > > x86_64-unknown-freebsd12.0 > > > > .. > > > > # gcc7 -dumpmachine > > x86_64-portbld-freebsd12.0 >=20 > That's not actually related to GCC, but the lang/gcc* ports using > the FreeBSD Ports Collection's default that explicitly set >=20 > Yes, I know. That's why I said the vendor part must be forced to = "unknown". >=20 >=20 > CONFIGURE_TARGET?=3D ${ARCH}-portbld-${OPSYS:tl}${OSREL} >=20 > By default GCC would use the same as clang. >=20 > Sure, but that doesn't mean the vendor part of the triple in the = default compiler is guaranteed to be 'unknown'. The "unknown" vs. "portbld" has a specific meaning for a FreeBSD context: unknown: it is a devel/* port portbld: it is a lang/* port This keeps the likes of devel/powerpc64-gcc and lang/gcc6 from having conflicting files on a powerpc64 FreeBSD machine, even when they are at the same (full) version. The variation that I intended to write about was the x86_64 vs. i386 variation when -m32 is in use. That is a separate issue from unknown vs. portbld . =3D=3D=3D Mark Millard markmi at dsl-only.net