Date: Sun, 29 Oct 2017 10:51:07 +0100 From: Stefan Esser <se@freebsd.org> To: freebsd-toolchain@freebsd.org Subject: Re: External LLVM toolchain not consistently locating c++ when compiling ports Message-ID: <ab00ced5-cd51-dc3c-aa4c-6b4dbe2d4a3c@freebsd.org> In-Reply-To: <3E01A2C6-0728-4295-90AE-76A7CE5955EF@dsl-only.net> References: <trinity-8d3dd393-342f-41d2-9781-0c9f7778b8d9-1509252017014@3c-app-mailcom-lxa12> <D285E708-6C34-43FC-9AD5-07215B6F04B4@dsl-only.net> <trinity-368804ee-950f-4283-a4db-21bf7a5870c8-1509261032035@3c-app-mailcom-lxa12> <3E01A2C6-0728-4295-90AE-76A7CE5955EF@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 29.10.17 um 08:48 schrieb Mark Millard:
> So without system clang (or system gcc 4.2.1) and only
> with llvm40 I expect that there is no c++ command at all.
> The issue would not be an overly-specific path: no path
> would work.
>
> Rust needs to not be looking for a c++ command at all.
> It needs to be using ${CXX} and the like that would
> need to involve clang++50 .
>
> But you can make a local workaround by creating your
> own c++ command someplace in the paths being checked,
> either linking to or copying clang++40 to produce the
> c++ . c++ might not be the only file needing such
> a technique.
This situation should be covered by the new BINARY_ALIAS feature,
which makes a symbolic link to some binary available under a new
name and adds the location of that link to the PATH:
https://svnweb.freebsd.org/ports?view=revision&revision=451772
In this particular case:
BINARY_ALIAS c++=clang++50
Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ab00ced5-cd51-dc3c-aa4c-6b4dbe2d4a3c>