Re: External LLVM toolchain not consistently locating c++ when compiling ports

2017-10-28 Thread Mark Millard
On 2017-Oct-28, at 9:40 PM, Sid wrote: > In /etc/make.conf, when I use, > XCC= /usr/local/bin/clang40 > XCXX= /usr/local/bin/clang++40 > XCPP= /usr/local/bin/clang-cpp40 > for ports that require c++ without clang in the base system, I get the error > code > make: "/usr/ports/Mk/Uses/compile

External LLVM toolchain not consistently locating c++ when compiling ports

2017-10-28 Thread Sid
In /etc/make.conf, when I use, XCC=/usr/local/bin/clang40 XCXX= /usr/local/bin/clang++40 XCPP= /usr/local/bin/clang-cpp40 for ports that require c++ without clang in the base system, I get the error code make: "/usr/ports/Mk/Uses/compiler.mk" line 112:warning: "c++ -### /dev/null 2>&1

Re: lib/clan/llvm.build.mk: Shouldn't BUILD_TRIPLE definition rely host 'cc -dumpmachine'?

2017-10-28 Thread Mark Millard
On 2017-Oct-28, at 4:11 AM, Dimitry Andric wrote: > On 27 Oct 2017, at 08:23, Eddy Petrișor wrote: >> >> I am trying to make the FreeBSD code base build from a Linux host and >> found this bit which defines BUILD_TRIPLE in a way which to my >> untrained eyes look like overengineering. >> >> .i

Re: lib/clan/llvm.build.mk: Shouldn't BUILD_TRIPLE definition rely host 'cc -dumpmachine'?

2017-10-28 Thread Dimitry Andric
On 27 Oct 2017, at 08:23, Eddy Petrișor wrote: > > I am trying to make the FreeBSD code base build from a Linux host and > found this bit which defines BUILD_TRIPLE in a way which to my > untrained eyes look like overengineering. > > .if ${TARGET_ARCH:Marmv6*} && (!defined(CPUTYPE) || ${CPUTYPE: