From owner-freebsd-current@freebsd.org Tue Aug 30 06:54:55 2016 Return-Path: Delivered-To: freebsd-current@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 2819EBC85C5 for ; Tue, 30 Aug 2016 06:54:55 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from limbo.b1t.name (limbo.b1t.name [78.25.32.206]) by mx1.freebsd.org (Postfix) with ESMTP id D4C9F642 for ; Tue, 30 Aug 2016 06:54:53 +0000 (UTC) (envelope-from arcade@b1t.name) Received: from [172.29.1.160] (probe.42.lan [172.29.1.160]) by limbo.b1t.name (Postfix) with ESMTPSA id D26A319D for ; Tue, 30 Aug 2016 09:46:53 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=b1t.name; s=mail; t=1472539614; bh=qGzyfzUqFcGAF88OLsS7Frh6z+zhCGrAjv/ydJR0Rlo=; h=Subject:To:References:From:Date:In-Reply-To; b=ewdXiJCgDk9CDuiYptvJkWmjvXPTGU2OI5w6bKDXYf90N9q1N3alY7+pkq/FO1aoG DHOCmo3KtMwGa10sMyHIaHBsWhpGjGRBd7eXYb0hbyNvWmBmtjqpUZG8SjTj6jkP3d EOx0ZrAekF8nhJDK9XucHk/8okDW8l4HAOvXbkuo= Subject: Re: External toolchain support broken for devel/llvm38 but not devel/llvm37 To: "freebsd-current@freebsd.org" References: <156d96ebba6.d2524daa80643.7192912559150916238@nextbsd.org> From: Volodymyr Kostyrko Message-ID: <57C52BDD.9020207@b1t.name> Date: Tue, 30 Aug 2016 09:46:53 +0300 User-Agent: Mozilla/5.0 (X11; DragonFly x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <156d96ebba6.d2524daa80643.7192912559150916238@nextbsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 30 Aug 2016 11:25:33 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2016 06:54:55 -0000 Matthew Macy wrote: > It looks like there is something broken with the devel/llvm38 port or external toolchain support has regressed: > > > This works: > make XCC=/usr/local/bin/clang37 XCXX=/usr/local/bin/clang++37 XCPP=/usr/local/bin/clang-cpp37 buildworld -j12 -s > > This fails: > make XCC=/usr/local/bin/clang38 XCXX=/usr/local/bin/clang++38 XCPP=/usr/local/bin/clang-cpp38 buildworld -j12 -s > > with: > > /home/mmacy/devel/build/mnt/storage/mmacy/devel/drm-next-merge/tmp/usr/bin/ld: /usr/local/llvm38/bin/../lib/clang/3.8.1/lib/freebsd/libclang_rt.ubsan_standalone-x86_64.a: No such file: No such file or directory > clang-3.8: error: linker command failed with exit code 1 (use -v to see invocation) I second this - I also faced it. I think this is not a problem with a ports but rather with a build as correspondent files can be found in /usr/obj under /usr/obj/usr/src/tmp/usr/lib/clang/3.8.0/lib/freebsd/. Looks like this files are compiled during build but taken from compilers's directory. Linking 'em to the target directory makes build succeed. -- Sphinx of black quartz judge my vow.