From owner-freebsd-current@freebsd.org Mon May 8 17:38:25 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 052D0D63356 for ; Mon, 8 May 2017 17:38:25 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3EB7A1CE for ; Mon, 8 May 2017 17:38:23 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([78.52.143.39]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LjLwB-1dkxNk2Yjn-00dU6D; Mon, 08 May 2017 19:38:11 +0200 Date: Mon, 8 May 2017 19:38:10 +0200 From: "O. Hartmann" To: "O. Hartmann" Cc: "Simon J. Gerraty" , Konstantin Belousov , FreeBSD CURRENT Subject: Re: filemon: weird full-time build although filemon enabled Message-ID: <20170508193810.3d683d2a@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20170508193258.4b0ddec2@thor.intern.walstatt.dynvpn.de> References: <20170506092255.083828f8@thor.intern.walstatt.dynvpn.de> <16322.1494224695@kaos.jnpr.net> <20170508173709.37e94b17@thor.intern.walstatt.dynvpn.de> <25259.1494259448@kaos.jnpr.net> <20170508162320.GD1622@kib.kiev.ua> <26642.1494263825@kaos.jnpr.net> <20170508193258.4b0ddec2@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/WTvXVZJQr54ZOX5.NiDOSq7"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:3C+x56xj5GEu2YQy6m+gq9kFVgxuQ4kRG5FVMNR8xVkudY+dEAA 3Xqxu86fS7aE0b0CW6jJDC3azzkh408SPzHFdkSqxKVUlO4osSP/80y+QyBjW60HzjXLPEp GaE+/RCItnhNQHen6LeVVHqILYLQOYvHHh4Kc+r8hq9FUlctinXUah9/xwEpzJZlmaY5kls 7Jzfs81XEWBKRWw20MeEQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:1Cf/NgOs9L0=:gP1H0ievlBEIXL7vlVlNPe PaRLkAL8aPkCbHF9Q3siI1/uvOkic605XFYP91n/uaU5VAs66mwj12ASd36mz/o1/MXX5iMu0 z3rDS3CPT/pgmIxOnW68Xsq/szgKP2XhBKxPwjnodWq9cP7Z4zDwTsI8GoF6vI0wUmnJCnRy0 +RogEQlc7tWgaqyB9jnHTvgRoDDNNii4GwMoNF4N8ICkPjPAms9abCVH1tpfQZdIYBNc32JBX IrhcpMq4sW9DyyHcmibm0UYH6roFUUeOiUAgKQMet1CcqWZPydyGUSzHizZUNbvJ+IHrNnbCV o3ZkMW7uVv+QKnin+7WbiCZPj3tkyiaTMgV6wX8QyCZQ79SGlzQwTXF3OVJk2YSgZdTeMfERx x3O9oDpsnWj8rGZg7d//4qWj+Ak9qWyEP5FXBUYAKQZhhXmYbF+nkd+0FQQqw3CAP2EJWsX1u oucNYKNdw+NS6vpY25QQi89rE19DMZaUFDdaiDq1YLJYdlzSr3hJV59d3N73mlOyDX8Nx3PcN B1bhySqTVQIdw9H3Hp0uPzb//tgbtcYdUsO1IKzC5HOEcwZm2pcBoMMCnDAKbM+tnekQ7L2bI rqyQiB40fmrJia+dlsqRioXdPNktTI3kru+r4Akj5xJK77yS8so7BD1mIMq1QEG4qfMIrO5j7 VlXxViGyfXVwSdrzzFvV7IRcA7Dh63CirxyHUOlhWGI9UjlgVpnaEWg3Tkjqjqms37AgTMq6B EENZh7ujtaD/wU+Afzr8iInKmY7oQmdshbiXUSnunsA071dUrqkdW/BaGcU= X-Mailman-Approved-At: Mon, 08 May 2017 18:04:55 +0000 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: Mon, 08 May 2017 17:38:25 -0000 --Sig_/WTvXVZJQr54ZOX5.NiDOSq7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Mon, 8 May 2017 19:32:58 +0200 "O. Hartmann" schrieb: > Am Mon, 8 May 2017 10:17:05 -0700 > "Simon J. Gerraty" schrieb: >=20 > > Konstantin Belousov wrote: =20 > > > If I understand the motto of meta-mode, any file change is detected f= or any > > > file accessed during the build. All dynamically-linked binary includ= es > > > the rtld into the process image, and rtld reads all config files in t= he > > > libmap.d subdirectories. The end result is that everything must be r= ebuild > > > if any config file changed. =20 > >=20 > > Ah. > > =20 > > > Then, after the world build, according to OP, the nvidia driver port = is > > > reinstalled, which installs the nvidia.conf anew, which triggers the > > > behaviour on the next build. =20 > >=20 > > Yes, that would account for it. > >=20 > > There are always exceptions - things we expect to be volatile and don't > > care - or for any other reason just want to ignore. > >=20 > > bmake has a set of knobs for telling it to ignore things. > > OP try > >=20 > > .MAKE.META.IGNORE_PATHS +=3D /usr/local/etc/libmap.d > >=20 > > --sjg =20 >=20 > I suppose I have to set this flag in=20 >=20 > /etc/src-env.conf >=20 > ? >=20 from empirical experience, it is neither of /etc/src.conf or /etc/src-env.c= onf nor does setting via "env" do something ... :-( --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/WTvXVZJQr54ZOX5.NiDOSq7 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWRCtAgAKCRDS528fyFhY lKP+Af9Ja0ZU9XPvdBd3Kw7sUDi6pj2vMJRic5RKkaf+JioZyDSPlGuvDmdzH/MB Fy4SJWFHjwt6MQqxvg9/BcuIGpKeAf94j6avFv4ja4HtJzvmhPVXy6KziRTAUAkF I61eIaUaSx3miF0uJ9MrT+n9Pb3zuCc8h6wfRjeKNDZSk2c6fH+I =hA0t -----END PGP SIGNATURE----- --Sig_/WTvXVZJQr54ZOX5.NiDOSq7--