From owner-freebsd-current@freebsd.org Thu May 11 19:56:52 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 BB481D69ED0 for ; Thu, 11 May 2017 19:56:52 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 7E61C1676; Thu, 11 May 2017 19:56:52 +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 9AC472B4D; Thu, 11 May 2017 19:56:51 +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 BE6A982EF; Thu, 11 May 2017 19:56:49 +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 8wRLNsh7IFst; Thu, 11 May 2017 19:56:46 +0000 (UTC) Subject: Re: make release: how utilise filemon? DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 50A9182E9 To: "O. Hartmann" , freebsd-current References: <20170510101231.374cc22a@freyja.zeit4.iv.bundesimmobilien.de> From: Bryan Drewery Organization: FreeBSD Message-ID: <0cf1254d-4c01-333f-6df3-f8755794b339@FreeBSD.org> Date: Thu, 11 May 2017 12:56:28 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <20170510101231.374cc22a@freyja.zeit4.iv.bundesimmobilien.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="w6O4McFGh31stM7ihGBOgjqHKb5heLjej" 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: Thu, 11 May 2017 19:56:52 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --w6O4McFGh31stM7ihGBOgjqHKb5heLjej Content-Type: multipart/mixed; boundary="uhVgWAXLMDF91RMgpX5CBm1UMkMdCo4NT"; protected-headers="v1" From: Bryan Drewery To: "O. Hartmann" , freebsd-current Message-ID: <0cf1254d-4c01-333f-6df3-f8755794b339@FreeBSD.org> Subject: Re: make release: how utilise filemon? References: <20170510101231.374cc22a@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20170510101231.374cc22a@freyja.zeit4.iv.bundesimmobilien.de> --uhVgWAXLMDF91RMgpX5CBm1UMkMdCo4NT Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 5/10/17 1:12 AM, O. Hartmann wrote: > hello, >=20 > building a release of most recent 12-CURRENT seems to be at some point = very > annoying. When building the main host's system out of /usr/src > using /etc/src-env.conf set with WITH_META_MODE=3Dyes, build time decre= ases > significantly. Now I perform some tasks building release. The source tr= ee is > 11-STABLE. >=20 > In release.conf, I tried setting >=20 > ## Set to use world- and kernel-specific make(1) flags. > WORLD_FLAGS=3D"-DNO_CLEAN -j $(sysctl -n hw.ncpu)" > KERNEL_FLAGS=3D"-DNO_CLEAN -j $(( $(( $(sysctl -n hw.ncpu) + 1 )) / 2 )= )" >=20 > without any noticable effect - make release always build release fully,= no > matter wether there has been new sources checked out or not. It takes a= lot of > time compiling llvm/clang. Using 11-stable on a NanoBSD installation, > -DNO_CLEAN seems to take effect on the very same source revision, while= it > doesn't on "make release". The target (obj-directory) is always properl= y set, > the same and not deleted by a run of "make release", so I'm quite sure = this > portion of the setting is correct. >=20 > release(7) does have some tags setting src.conf, but I miss src-env.con= f > settings as this can be customised in the "ordinary" /usr/src world. >=20 > What am I doing or thinking wrong in this matter? >=20 > Kind regards, >=20 > Oliver > _______________________________________________ META_MODE is only allowed in a whitelist of targets (see META_TGT_WHITELIST in Makefile). I wanted to avoid META MODE ever being enabled for an 'install' target or utility target like 'check-old' or 'delete-old', etc. META MODE has the potential to skip doing things that are actually needed, like copying a file to /. So I decided to whitelist to known-safe targets. The 'make release' target, and all of release/, is something I've never ran and am not very familiar with, so I didn't list it. Thus WITH_META_MODE=3Dyes and 'make release' has no effect, it will build without META MODE. In summary, support needs to be added for release/ in safe and useful way= s. --=20 Regards, Bryan Drewery --uhVgWAXLMDF91RMgpX5CBm1UMkMdCo4NT-- --w6O4McFGh31stM7ihGBOgjqHKb5heLjej Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJZFMHtAAoJEDXXcbtuRpfPZVUIANNhCYLCmY5/biAGhZzmOAVq f8jtU0Q5am/qfHIUmlaHclyGvGorws/96fBVHl/U5nFZ/siNyhMKAdL9jjRtLOgf /4pO/kI784l/pkgrOhQ+bi9Rr2cph5kSvdUOnvh0Jr0vvXhEax5brs6KbDcT7gMl A5MtTfZN0BuFd/NkscB3wU6eW5ztwAJ+cWYDqo2S6689pv7XUU5qez8asFYr6sU5 8NKgH02gzGFauULy+rCI66/FX80DYxb3bzhfl/YTdAISxq3HSI9KnWwfqKbrMuKL aMXGzgI12cXkGwsqxcgtmQJahyJydvovqGheZo6KkZPcgcWypBKvLZ+XMv7eYlg= =F/va -----END PGP SIGNATURE----- --w6O4McFGh31stM7ihGBOgjqHKb5heLjej--