Date: Sun, 5 Nov 2017 02:19:15 +0200 From: =?UTF-8?Q?Eddy_Petri=C8=99or?= <eddy.petrisor@gmail.com> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: Mark Millard <markmi@dsl-only.net>, 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: <CAK0XTWdUbwqfkXu%2B2bpmUGPLtPu_%2B3hEr1fdWeg4KosKW0QXQA@mail.gmail.com> In-Reply-To: <alpine.LSU.2.21.1711042354060.4053@anthias.pfeifer.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>
index | next in thread | previous in thread | raw e-mail
Pe 5 nov. 2017 12:57 AM, "Gerald Pfeifer" <gerald@pfeifer.com> a scris:
On Sun, 29 Oct 2017, Eddy Petrișor 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
That's not actually related to GCC, but the lang/gcc* ports using
the FreeBSD Ports Collection's default that explicitly set
Yes, I know. That's why I said the vendor part must be forced to "unknown".
CONFIGURE_TARGET?= ${ARCH}-portbld-${OPSYS:tl}${OSREL}
By default GCC would use the same as clang.
Sure, but that doesn't mean the vendor part of the triple in the default
compiler is guaranteed to be 'unknown'.
Eddy Petrișor
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAK0XTWdUbwqfkXu%2B2bpmUGPLtPu_%2B3hEr1fdWeg4KosKW0QXQA>