From owner-freebsd-toolchain@freebsd.org Fri Nov 3 19:59:48 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 B28A4E59CAA; Fri, 3 Nov 2017 19:59:48 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7831870E3A; Fri, 3 Nov 2017 19:59:48 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id A277DCF0; Fri, 3 Nov 2017 19:59:47 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id D31EA28E1; Fri, 3 Nov 2017 19:59:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id bROGNdKSJApM; Fri, 3 Nov 2017 19:59:43 +0000 (UTC) Subject: sys/boot machine symlink dirs causing rebuild [was Re: Example of Bryan Drewery's "Something is very wrong" ...] DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com B140A28DC To: Mark Millard Cc: freebsd-hackers , FreeBSD Toolchain , FreeBSD Current References: <40F1D1F0-A67D-4BF9-9936-EF07A9E01912@dsl-only.net> <83ae760f-7bd5-811c-f32e-9d8f03074b49@FreeBSD.org> <20E6AE67-83F8-40D5-A4DA-01C02FA0A02B@dsl-only.net> <6E2B2A5E-A52E-4027-B73B-C6E78D9C0EED@dsl-only.net> <8D698E5D-C986-4FBA-BD56-6BA4E7D7F519@dsl-only.net> <12bff2b7-655d-b236-5f96-d405870e53d0@FreeBSD.org> <25840EFC-69DD-4A2A-B89A-0D6D51C9BA14@dsl-only.net> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: Date: Fri, 3 Nov 2017 12:59:27 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <25840EFC-69DD-4A2A-B89A-0D6D51C9BA14@dsl-only.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cpHBcDaQVNXKcv8H5hLaoTSPt7QovStJR" 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: Fri, 03 Nov 2017 19:59:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --cpHBcDaQVNXKcv8H5hLaoTSPt7QovStJR Content-Type: multipart/mixed; boundary="gH2GsuUNtt2oJg0voc1V9xcdpDwdJCvVs"; protected-headers="v1" From: Bryan Drewery To: Mark Millard Cc: freebsd-hackers , FreeBSD Toolchain , FreeBSD Current Message-ID: Subject: sys/boot machine symlink dirs causing rebuild [was Re: Example of Bryan Drewery's "Something is very wrong" ...] References: <40F1D1F0-A67D-4BF9-9936-EF07A9E01912@dsl-only.net> <83ae760f-7bd5-811c-f32e-9d8f03074b49@FreeBSD.org> <20E6AE67-83F8-40D5-A4DA-01C02FA0A02B@dsl-only.net> <6E2B2A5E-A52E-4027-B73B-C6E78D9C0EED@dsl-only.net> <8D698E5D-C986-4FBA-BD56-6BA4E7D7F519@dsl-only.net> <12bff2b7-655d-b236-5f96-d405870e53d0@FreeBSD.org> <25840EFC-69DD-4A2A-B89A-0D6D51C9BA14@dsl-only.net> In-Reply-To: <25840EFC-69DD-4A2A-B89A-0D6D51C9BA14@dsl-only.net> --gH2GsuUNtt2oJg0voc1V9xcdpDwdJCvVs Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 11/3/2017 12:42 PM, Mark Millard wrote: > On 2017-Nov-3, at 11:31 AM, Bryan Drewery wrote:= >=20 >> On 11/3/17 1:52 AM, Mark Millard wrote: >>> I did get another problem after buildworld, buildkernel, installkerne= l >>> without future source code dates: the installworld got a "cc not foun= d" >>> for the amd64 native build based on -r325351 --that also appears to b= e >>> set up to report: >>> >>> ERROR-tried-to-rebuild-during-make-install >>> >>> if cc had been found: >>> >>> .if defined(SRCTOP) >>> # Prevent rebuilding during install to support read-only objdirs. >>> .if ${.TARGETS:M*install*} =3D=3D ${.TARGETS} && empty(.MAKE.MODE:Mme= ta) >>> CFLAGS+=3D ERROR-tried-to-rebuild-during-make-install >>> .endif=20 >>> .endif=20 >>> >> >> This one usually only happens if it is trying to compile at installtim= e, >> which usually means a file is missing (wrong OBJDIR perhaps) or the >> timestamps are off. >> >> I'll play with this more and see what I can come up with, but I didn't= >> run into anything like this myself yet. >=20 > I locally forced a -dm on the ${MAKE} command involved > and the result reported: >=20 > Examining beforeinstall...non-existent....PHONY node...out-of-date. > recheck(beforeinstall): update time from 16:00:00 Dec 31, 1969 to now > Examining machine...modified 20:13:03 Nov 03, 2017...up-to-date. > Examining x86...modified 20:13:07 Nov 03, 2017...up-to-date. > Examining autoload.c...modified 2:27:17 Nov 03, 2016...up-to-date. > Examining autoload.o...modified 0:10:12 Nov 03, 2017...modified before= source x86...out-of-date. > cc -target x86_64-unknown-freebsd12.0 --sysroot=3D/usr/obj/amd64_clang/= amd64.amd64/usr/src/amd64.amd64/tmp -B/usr/obj/amd64_clang/amd64.amd64/us= r/src/amd64.amd64/tmp/usr/bin -O2 -pipe -ffreestanding -Wformat -mno-m= mx -mno-sse -mno-avx -msoft-float -fshort-wchar -mno-red-zone -mno-aes -D= LOADER_UFS_SUPPORT -DLOADER_DISK_SUPPORT -DLOADER_GPT_SUPPORT -DLOADER_MB= R_SUPPORT -DLOADER_GELI_SUPPORT -I/usr/src/sys/boot/libsa -I/usr/src/sys/= boot/zfs -DEFI_ZFS_BOOT -fPIC -DTERM_EMU -I/usr/src/sys/boot/efi/loader -= I/usr/src/sys/boot/efi/loader/arch/amd64 -I/usr/src/sys/boot/efi/include = -I/usr/src/sys/boot/efi/include/amd64 -I/usr/src/sys/contrib/dev/acpica/i= nclude -I/usr/src/sys -I/usr/src/sys/boot/i386/libi386 -DNO_PCI -DEFI -DS= MBIOS_SERIAL_NUMBERS -I/usr/src/sys/boot/common -fPIC -I/usr/src/sys/boot= /ficl -I/usr/src/sys/boot/ficl/amd64 -I/usr/src/sys/boot/common -DBOOT_FO= RTH -DBF_DICTSIZE=3D15000 -g -std=3Dgnu99 -Wsystem-headers -Wall -Wno-fo= rmat-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototype= s -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -W= no-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -= Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum= -conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Qun= used-arguments ERROR-tried-to-rebuild-during-make-install -c /usr/src/sy= s/boot/efi/loader/autoload.c -o autoload.o > /tmp/install.intsn5IS/sh: cc: not found > *** Error code 127 >=20 > So far I've not found anything with matching times for: >=20 > Examining machine...modified 20:13:03 Nov 03, 2017...up-to-date. > Examining x86...modified 20:13:07 Nov 03, 2017...up-to-date. >=20 > But the reason for rebuild is listed as: >=20 > modified before source x86...out-of-date. >=20 > I'll keep looking. The odd time (future) is in the > ball park of others from when the virtual machine > apparently had a bad time setting. >=20 > I'm not sure if the x86 is a file vs. a directory > here. A directory would seem a bit strange for > forcing a rebuild. (Similarly for machine.) It's these dependencies on a symlink: sys/boot/efi/boot1/Makefile:beforedepend ${OBJS}: x86 sys/boot/efi/loader/Makefile:beforedepend ${OBJS}: x86 A similar symlink is done for kernel modules but it avoids the problem you're hitting through various fixes such as in r72935 and r315459. I'll work on a fix. (It's unrelated to my recent changes) >=20 > =3D=3D=3D > Mark Millard > markmi at dsl-only.net >=20 --=20 Regards, Bryan Drewery --gH2GsuUNtt2oJg0voc1V9xcdpDwdJCvVs-- --cpHBcDaQVNXKcv8H5hLaoTSPt7QovStJR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJZ/MqgAAoJEDXXcbtuRpfPyWIH/24lgYdX+y0hnEqIlC4HE8Ib jC5AvvGjVuccU1+vlkUpygd0555Sa/SmOL+wDuVeMYwTOMO/tg4hq+bZhzVRjmJc sKeKHLSXhIrdbrIPV3HhNdkdozBqBe49HqD8hm9hN3JMwrl6XMjBlH83sZ+jIqQX BP05EwnOTrLfgFbKgbP1nqOrMCaj5YvLphUrx5GlOFpLG2VMdIy6o6ZzYQu+EjIp TR2w6CNcKlyoNVfe+gyIp3ntCxuCjHgNwtrtB+nLv+EJR3hjNRa5q92tU7lMez6M O99toYYM1RUrwC/0jS+17NGbUHIBFvOZSgL0/MrOxMqwiQ9abh+coAVuQkk+S8Q= =nYgb -----END PGP SIGNATURE----- --cpHBcDaQVNXKcv8H5hLaoTSPt7QovStJR--