Date: Sat, 4 Nov 2017 18:02:16 -0700 From: Mark Millard <markmi@dsl-only.net> To: =?utf-8?Q?Eddy_Petri=C8=99or?= <eddy.petrisor@gmail.com> Cc: Gerald Pfeifer <gerald@pfeifer.com>, freebsd-arm@freebsd.org, freebsd-toolchain@freebsd.org, Dimitry Andric <dim@freebsd.org> Subject: Re: [toolchain] lib/clan/llvm.build.mk: Shouldn't BUILD_TRIPLE definition rely host 'cc -dumpmachine'? Message-ID: <12E66105-6E1D-4941-B4C4-3BBAC0F3B330@dsl-only.net> In-Reply-To: <CAK0XTWdUbwqfkXu%2B2bpmUGPLtPu_%2B3hEr1fdWeg4KosKW0QXQA@mail.gmail.com> References: <CAK0XTWczya8vg_sQZPqz-ZyYZRMq1v6p%2Bjs90S%2BjaDHxo2=1gA@mail.gmail.com> <CDAA0CB5-F1FC-40FE-AEC5-56FD64654671@FreeBSD.org> <7CAFD8CC-BDA1-4E89-BD7E-D0089E27036F@dsl-only.net> <CAK0XTWdRjek6StRktBfn0oGMo1ixTohs6NPoyDx__QMQ56ki_g@mail.gmail.com> <alpine.LSU.2.21.1711042354060.4053@anthias.pfeifer.com> <CAK0XTWdUbwqfkXu%2B2bpmUGPLtPu_%2B3hEr1fdWeg4KosKW0QXQA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Nov-4, at 5:19 PM, Eddy Petri=C8=99or <eddy.petrisor at =
gmail.com> wrote:
> Pe 5 nov. 2017 12:57 AM, "Gerald Pfeifer" <gerald at pfeifer.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12E66105-6E1D-4941-B4C4-3BBAC0F3B330>