From owner-freebsd-current@freebsd.org Mon Jun 13 22:21:54 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 D29E1AF2C58 for ; Mon, 13 Jun 2016 22:21:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-154.reflexion.net [208.70.211.154]) (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 70B412B30 for ; Mon, 13 Jun 2016 22:21:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 25429 invoked from network); 13 Jun 2016 22:22:27 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 13 Jun 2016 22:22:27 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.90.3) with SMTP; Mon, 13 Jun 2016 18:21:57 -0400 (EDT) Received: (qmail 7193 invoked from network); 13 Jun 2016 22:21:57 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 13 Jun 2016 22:21:57 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.0.105] (ip70-189-131-151.lv.lv.cox.net [70.189.131.151]) by iron2.pdx.net (Postfix) with ESMTPSA id 86AAAB1E002; Mon, 13 Jun 2016 15:21:47 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: WITH_META_MODE vs. delete-old and delete-old-libs From: Mark Millard In-Reply-To: Date: Mon, 13 Jun 2016 15:21:50 -0700 Cc: Bryan Drewery , FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: <4E762402-95A9-4A2C-B2CE-B0551E5BBB31@dsl-only.net> References: <31063879-DF43-4895-A9EA-99A70DCFE4A1@dsl-only.net> To: Ngie Cooper X-Mailer: Apple Mail (2.3124) 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: Mon, 13 Jun 2016 22:21:54 -0000 On 2016-Jun-13, at 2:51 PM, Ngie Cooper wrote: > On Mon, Jun 13, 2016 at 2:12 PM, Mark Millard = wrote: >> I've been using the following script to run my make commands for = amd64 builds (as an example): >>=20 >>> # more = ~/sys_build_scripts.amd64-host/make_amd64_nodebug_clang_bootstrap-amd64-ho= st.sh >>> kldload -n filemon && \ >>> script = ~/sys_typescripts/typescript_make_amd64_nodebug_clang_bootstrap-amd64-host= -$(date +%Y-%m-%d:%H:%M:%S) \ >>> env __MAKE_CONF=3D"/root/src.configs/make.conf" = SRC_ENV_CONF=3D"/root/src.configs/src.conf.amd64-clang-bootstrap.amd64-hos= t" \ >>> WITH_META_MODE=3Dyes \ >>> MAKEOBJDIRPREFIX=3D"/usr/obj/clang/amd64.amd64" \ >>> make $* >>=20 >> When the WITH_META_MODE=3Dyes is present (as shown) delete-old and = delete-old-libs command line arguments to the script do not display the = prompts but the process does wait for the y/n answers. I've actually = used top in another window to see what it is waiting for an answer to. = After I've answered all the questions then the list of prompts finally = is shown all at once. >>=20 >> Without WITH_META_MODE=3D each prompt text is displayed before it = waits for the answer to that prompt. >>=20 >>=20 >> This sort of fits in with my earlier questions about make usage that = is in the likes of, say, mergemaster and if/where care about = WITH_META_MODE=3Dyes use vs. disuse might be important for such. For = example: Should "env WITH_META_MODE=3Dyes" be used with mergemaster if = it was used with buildworld, buildkernel, installkernel, and = installworld? >=20 > I generally do: >=20 > yes | sudo make delete-old >=20 > Cheers, > -Ngie For my amd64, rpi2, and powerpc (non-64) activities I can do such things = rather than answer prompts individually --and have sometimes. But for my libc++/xtoolchain based powerpc64 environment I've got a = couple of things it lists for delete-old that I do not want deleted = because I've got special things in place. If the check-old list is = fairly short I answer delete-old individually. If the check-old list is = really long I delete all and run a script that puts back my couple of = oddities (which happen to be symbolic links). Thus I tend to expect and use the individual delete-old prompts at least = for one of my contexts. I do have a tendency to work similarly across contexts even when local = optimizations could be made. So I tend to treat amd64, armv6, powerpc = similar to powerpc64 for check-old/delete-old use. [Another example: I'm = unlikely to use ports-mgmt/synth on amd64 because I can not use it on = armv6, powerpc, or powerpc64.] And that explains why I noticed the issue even though I currently do not = have access to the powerpc64 or powerpc machines. =3D=3D=3D Mark Millard markmi at dsl-only.net