From owner-freebsd-current@freebsd.org Tue Aug 30 21:08:48 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 3543BBC806B for ; Tue, 30 Aug 2016 21:08:48 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15ECE9F6 for ; Tue, 30 Aug 2016 21:08:47 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id C34425A9F27; Tue, 30 Aug 2016 21:08:41 +0000 (UTC) Date: Tue, 30 Aug 2016 21:08:41 +0000 From: Brooks Davis To: Matthew Macy Cc: "freebsd-current@freebsd.org" Subject: Re: External toolchain support broken for devel/llvm38 but not devel/llvm37 Message-ID: <20160830210841.GA25000@spindle.one-eyed-alien.net> References: <156d96ebba6.d2524daa80643.7192912559150916238@nextbsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline In-Reply-To: <156d96ebba6.d2524daa80643.7192912559150916238@nextbsd.org> User-Agent: Mutt/1.6.1 (2016-04-27) 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 21:08:48 -0000 --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 29, 2016 at 08:12:08PM -0700, Matthew Macy wrote: > It looks like there is something broken with the devel/llvm38 port or ext= ernal toolchain support has regressed: >=20 >=20 > This works: > make XCC=3D/usr/local/bin/clang37 XCXX=3D/usr/local/bin/clang++37 XCPP= =3D/usr/local/bin/clang-cpp37 buildworld -j12 -s >=20 > This fails: > make XCC=3D/usr/local/bin/clang38 XCXX=3D/usr/local/bin/clang++38 XCPP= =3D/usr/local/bin/clang-cpp38 buildworld -j12 -s >=20 > with: >=20 > /home/mmacy/devel/build/mnt/storage/mmacy/devel/drm-next-merge/tmp/usr/bi= n/ld: /usr/local/llvm38/bin/../lib/clang/3.8.1/lib/freebsd/libclang_rt.ubsa= n_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 i= nvocation) I've fixed the install problem. I'm rather confused about why clang would try to link with sanitizer libraries when building source. That's certainly not default behavior. -- Brooks --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJXxfXZAAoJEKzQXbSebgfAox0H/0QxTwtmMTRRHOegeHjc06Kq 7TwU9h2607z/7xhWyg155DjoNz57aGp7KjZuLlAhkZPs6+4GI0m8xL/aFC0nCn8X heRn0J2J3nM/+yRenEXmSTn6HM3W9f/mIbwNkaNDaAGruRKYUtQXz6bufnI5hUkK 7bxvDZD/eQJvZwpgo13Iwr8pmodYFewO804wlWLI8VxlN4zP6JP3L7ycl68hFepi 9y7qAERcDpfcAPUOpKtM5QiS3JG3foE33Dyqg3hBHtt489bWFll27oBfPZ97A9Kk GBqNF34o7W3jdMr2mACdadhS/Enu7bGty5D7iD9Xei4m1P0+6leni+DpEM1xaC0= =cos1 -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+--