Date: Sat, 28 Oct 2017 22:11:18 -0700 From: Mark Millard <markmi@dsl-only.net> To: Sid <sid@bsdmail.com> Cc: freebsd-toolchain@freebsd.org Subject: Re: External LLVM toolchain not consistently locating c++ when compiling ports Message-ID: <D285E708-6C34-43FC-9AD5-07215B6F04B4@dsl-only.net> In-Reply-To: <trinity-8d3dd393-342f-41d2-9781-0c9f7778b8d9-1509252017014@3c-app-mailcom-lxa12> References: <trinity-8d3dd393-342f-41d2-9781-0c9f7778b8d9-1509252017014@3c-app-mailcom-lxa12>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-Oct-28, at 9:40 PM, Sid <sid at bsdmail.com> wrote: > In /etc/make.conf, when I use, > XCC=3D /usr/local/bin/clang40 > XCXX=3D /usr/local/bin/clang++40 > XCPP=3D /usr/local/bin/clang-cpp40 > for ports that require c++ without clang in the base system, I get the = error code=20 > make: "/usr/ports/Mk/Uses/compiler.mk" line 112:warning: "c++ -### = /dev/null 2>&1" returned non-zero status Quoting https://wiki.freebsd.org/ExternalToolchain: XCC The XCC approach works with top level build targets (buildworld, = buildkernel, etc) and overrides common make variables such as CC, CXX, = and AS during the cross building portions of the build with values = specified by the XCC, XCPP, XAS, etc variables. This method touches few = files and is relatively easy to understand, but has drawbacks including = the inability to build individual programs easily.=20 END QUOTE. Does ports support "cross building" that would be expected to use XCC, XCXX, XCPP, and the like? To my knowledge there is no cross build environment for ports that can avoid qemu (or an equivalent): cross builds of parts are based on qemu, which use CC, CXX, CPP and the like as far as I know. > Base and the kernel builds well with this setting. Compiles that don't = need c++ also work with this setting. Unlike for ports builds. (That is my understanding.) > I've compensated by adding > CC=3D /usr/local/bin/clang40 > CXX=3D /usr/local/bin/clang++40 > CPP=3D /usr/local/bin/clang-cpp40 > to the above. While this works for many ports requiring c++, it = doesn't work for Rust, and programs that depend on it (Firefox, = Thunderbird). This is what I'd expect for "self hosted" (target=3Dbuild) types of contexts and for being in a qemu context that looks like the target. I'm not aware of another form of cross build for FreeBSD ports. (I'd like to be able to do powerpc64 and powerpc without a system qemu. User qemu does not work for targeting powerpc64 or for powerpc.) > It seems that XCXX is supposed to replace CXX fully, considering that = XCC replaces CC, and XCPP replaces CPP when compiling other ports. Can you provide evidence of this? Does the evidence involve cross building where the X prefix is involved? > The error message for compiling rust with all of the above (XCC, XCXX, = XCPP, CC, CXX, CPP) set is > couldn't find required command: "c++" Does the environment not have a c++ command in a place listed in path? Otherwise it should be found. > This error happens whether the port option for lang/rust is set to = compile with llvm40 or the bundled version. > This is affected by /usr/ports/Mk/Uses/compiler.mk and I think this = problem affects ports compiled with c++ in the base system as well. =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?D285E708-6C34-43FC-9AD5-07215B6F04B4>