From owner-freebsd-current@freebsd.org Sun Jul 23 00:10:09 2017 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 21FFEDB1744; Sun, 23 Jul 2017 00:10:09 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF6896A66F; Sun, 23 Jul 2017 00:10:08 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from [IPv6:2001:470:7a58::e4cb:e9ff:2f5b:885e] (unknown [IPv6:2001:470:7a58:0:e4cb:e9ff:2f5b:885e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 301F0261A5; Sun, 23 Jul 2017 02:10:08 +0200 (CEST) From: Dimitry Andric Message-Id: <3EF869EB-ADB6-455B-8725-2E42C73B27EB@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_BD6F501B-F2F1-4E75-87B0-3F70204BFF0C"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: amd64 -r321109 -> -r321371 buildworld update failed (spans clang 5 update); error: too few arguments provided to function-like macro invocation; , METAMODE and -j8 was used Date: Sun, 23 Jul 2017 02:09:58 +0200 In-Reply-To: Cc: Bryan Drewery , FreeBSD Toolchain , FreeBSD Current To: Mark Millard References: <056C30CC-72B8-41A4-AEAA-64B6B96854DB@dsl-only.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Sun, 23 Jul 2017 00:10:09 -0000 --Apple-Mail=_BD6F501B-F2F1-4E75-87B0-3F70204BFF0C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 23 Jul 2017, at 02:02, Mark Millard wrote: >=20 > On 2017-Jul-22, at 4:50 PM, Dimitry Andric wrote: >> On 23 Jul 2017, at 01:32, Mark Millard wrote: >>>=20 >>> My first attempt to update amd64 to a clang 5 based /usr/src >>> failed ( -r321109 -> -r321371 ). Listing just the first >>> error initially: >>>=20 >>> --- ToolDrivers/llvm-lib/LibDriver.o --- >>> In file included from = /usr/src/contrib/llvm/lib/ToolDrivers/llvm-lib/LibDriver.cpp:35: >>> = /usr/obj/amd64_clang/amd64.amd64/usr/src/lib/clang/libllvm/Options.inc:27:= 92: error: too few arguments provided to function-like macro invocation >>> OPTION(prefix_0, "", INPUT, Input, INVALID, INVALID, nullptr, = 0, 0, nullptr, nullptr) >>> = ^ >>> /usr/src/contrib/llvm/lib/ToolDrivers/llvm-lib/LibDriver.cpp:34:9: = note: macro 'OPTION' defined here >>> #define OPTION(_1, _2, ID, _4, _5, _6, _7, _8, _9, _10, _11, _12) = OPT_##ID, >>> ^ >>=20 >> Yeah, I think this can happen with an incremental build, and if you >> enable MK_CLANG_EXTRAS. There was only one Options.inc file first, = in >> $WORLDTMP/usr/src/lib/clang/libllvm, but now there are two different >> ones, under $WORLDTMP/usr/src/lib/clang/libllvm/llvm-lib and >> $WORLDTMP/usr/src/lib/clang/libllvm/llvm-dlltool. This is a rather >> unfortunate change from upstream. >>=20 >> I'm unsure what to do here, maybe it is a good idea to explicitly rm >> the incorrect file before make starts to search the directory. = Bryan, >> any clues? IIRC there were some other precedents where stale objects >> could get in the way, and would have to be force-deleted before even >> the depend stage? >=20 > I've done: >=20 > # mv /usr/obj/amd64_clang /usr/obj/amd64_clang_r321109_r321371 >=20 > before starting a rebuild --in to preserve my > failed-build context in case that record of > the result of the attempt can help. What you could try with the old objdir is: rm = /usr/obj/amd64_clang/amd64.amd64/usr/src/lib/clang/libllvm/Options.inc then doing another incremental build. I think that will work. -Dimitry --Apple-Mail=_BD6F501B-F2F1-4E75-87B0-3F70204BFF0C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.1 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWXPpVgAKCRCwXqMKLiCW o3EyAJwPxn7fNzTVA8antRvqRQhBaI64+ACg9toU864msrbeiZocHlkM8r1cB4Y= =3rJP -----END PGP SIGNATURE----- --Apple-Mail=_BD6F501B-F2F1-4E75-87B0-3F70204BFF0C--