From owner-freebsd-toolchain@freebsd.org Sun Oct 29 09:51:17 2017 Return-Path: Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C6ACE5EFC6 for ; Sun, 29 Oct 2017 09:51:17 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout12.t-online.de (mailout12.t-online.de [194.25.134.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 306C873A9E for ; Sun, 29 Oct 2017 09:51:17 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd24.aul.t-online.de (fwd24.aul.t-online.de [172.20.26.129]) by mailout12.t-online.de (Postfix) with SMTP id 1C9C441DCE23 for ; Sun, 29 Oct 2017 10:51:09 +0100 (CET) Received: from Stefans-MBP-2.fritz.box (ZeoAlyZDZh-W8cEbN1XUHSh0kRrHGiMK+R-yujL09cQ9O8-6tGnHeaNt8f2TQ-IgxZ@[84.154.121.171]) by fwd24.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1e8kFI-3eob7g0; Sun, 29 Oct 2017 10:51:08 +0100 Subject: Re: External LLVM toolchain not consistently locating c++ when compiling ports To: freebsd-toolchain@freebsd.org References: <3E01A2C6-0728-4295-90AE-76A7CE5955EF@dsl-only.net> From: Stefan Esser Message-ID: Date: Sun, 29 Oct 2017 10:51:07 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <3E01A2C6-0728-4295-90AE-76A7CE5955EF@dsl-only.net> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ID: ZeoAlyZDZh-W8cEbN1XUHSh0kRrHGiMK+R-yujL09cQ9O8-6tGnHeaNt8f2TQ-IgxZ X-TOI-MSGID: 312873bc-0440-4139-993d-619eca5a42f6 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Oct 2017 09:51:17 -0000 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