From owner-freebsd-toolchain@freebsd.org Mon Oct 30 17:15:30 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 0FD62E624BC for ; Mon, 30 Oct 2017 17:15:30 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from mout.gmx.com (mout.gmx.com [74.208.4.200]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mail.gmx.com", Issuer "thawte SSL CA - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BD0126B193; Mon, 30 Oct 2017 17:15:29 +0000 (UTC) (envelope-from sid@bsdmail.com) Received: from [108.70.50.7] by 3c-app-mailcom-lxa05.server.lan (via HTTP); Mon, 30 Oct 2017 18:15:23 +0100 MIME-Version: 1.0 Message-ID: From: Sid To: "Stefan Esser" , freebsd-toolchain@freebsd.org Subject: Re: External LLVM toolchain not consistently locating c++ when compiling ports Content-Type: text/plain; charset=UTF-8 Date: Mon, 30 Oct 2017 18:15:23 +0100 Importance: normal Sensitivity: Normal In-Reply-To: References: <3E01A2C6-0728-4295-90AE-76A7CE5955EF@dsl-only.net> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K1:PD6S5QZpBhIj+i5/SOSTrF0lItE07L9qXYxx34GGMKF wk0N59zGWWQrdsT5HZvX1+EBPUo6WNBAKLEHqPhLh1kj4BBgjW DLQYaKBu6o1Cv2PwrqEYMuU1VvXzzuzijWF6ww1FeEQ0Bh+Qmq OomHBhNOpnlKWUJzQ4DsPKSDDGUYO7Ppu26YxjV1uYK6ie1HxJ DRwfQGopKot6+UHRYxQ03h4TeT9sKHAdST2J4vzCEepyDZIVBB CddB9n8+F6D2XCwcqusu0V9LwTa4sX/wn7Gs0iD8D5Eb5SlA04 mcXoxM= X-UI-Out-Filterresults: notjunk:1;V01:K0:O23T0f4bLXA=:ofRVMob1UGTCmI6DLSXb3M UWjvedes59Mk7HRDNv35IbimXjHB8iYKuCTlykHpU1CAGfTOP+CppE2xaEiVEOPC08eQFwy/G xM56ceXbvdadstCCcbnA4YqLZStV4UCS5x4bTg4g4WXG93KLvADecVtm9/VhynunNbSDXau/N 2U3XuEC21Q1tGvkkbeU9OAQl4E/M2bHe1l2/mzQXS1WQLJcjdXGfkpSDDc78u7QS+3hgpiy8B ROn4v8G0UAXEE5p5FoT5XpsNMK/SN2Nlu3bKnKCsPUoHdM4s0oz1qsuFsK0DQdxr3QeBS7K3t XHMf3NpNFjoDO6U6VOLrQ8aZMhBW9o4x9qF2ftYw6g/ulMAiV44KAOyA/2pO2NRBx/g8gfB34 3T0OC+vq5PLuYjQXw/6Q4mSgzqhSB4yK8has3+2QFcFeE2Wa1uAPIUGJbzf9NMa3ASMuVUxou YjbAi37CXK1oF7KgeTzrpfKrvv5wMrTnH3XEnoA9R/5B89RW1gWr+093aBChpk33Z1bh1GByq hb4gJS+Wfktf5aymsJ01P3c6llvT5qINA0jDXOUg61d 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: Mon, 30 Oct 2017 17:15:30 -0000 > Sent: Sunday, October 29, 2017 at 4:52 AM > From: "Stefan Esser" > To: Sid > Subject: Re: External LLVM toolchain not consistently locating c++ when compiling ports > > Am 29.10.17 um 10:46 schrieb Sid: > > Of course llvm50++ or llvm40++ as c++. The problem was naming. I've thought about using links before, but was worried to make too many changes like that. This time using llvm50, I've added two softlinks one in the directory of /usr/local/bin from c++ to clang++50, and in the directory of /usr/local/llvm50/bin/ from c++ to clang. This builds. It's not done yet, but I think this is it. I've added this to the bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223009 . It is about aarch64, but this problem applies to many architectures. Thank you. > > See BINARY_ALIAS in bsd.port.mk: > > https://svnweb.freebsd.org/ports?view=revision&revision=451772 > > Regards, STefan > As Mr. Millard suggested, this goes into /etc/make.conf BINARY_ALIAS= I've tried BINARY_ALIAS= c++=clang++50 BINARY_ALIAS= /usr/local/bin/c++=/usr/local/bin/clang++50 /usr/local/llvm50/bin/c++=/usr/local/llvm50/bin/clang-5.0 and the second example without the first "/" before "usr" There are two different targets from c++ in two directories (as in the examples; in /usr/local/llvm50/bin/, clang++ links to clang-5.0). I've tried this with the examples above, and it didn't work. There's more to BINARY_ALIAS. The soft links I've used for both directories, ln -s clang++50 c++, and ln -s clang-5.0 c++, have worked for compiling rust. It was mentioned in a bug report, but I'm emailing the maintainers of rust. Thank you