Date: Mon, 13 Jun 2016 15:21:50 -0700 From: Mark Millard <markmi@dsl-only.net> To: Ngie Cooper <yaneurabeya@gmail.com> Cc: Bryan Drewery <bdrewery@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: WITH_META_MODE vs. delete-old and delete-old-libs Message-ID: <4E762402-95A9-4A2C-B2CE-B0551E5BBB31@dsl-only.net> In-Reply-To: <CAGHfRMBbBnCOeWK4g-bqxJqzMaKE4Fs3TdL08E%2BfWxXGLLAEWQ@mail.gmail.com> References: <31063879-DF43-4895-A9EA-99A70DCFE4A1@dsl-only.net> <CAGHfRMBbBnCOeWK4g-bqxJqzMaKE4Fs3TdL08E%2BfWxXGLLAEWQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-Jun-13, at 2:51 PM, Ngie Cooper <yaneurabeya@gmail.com> wrote: > On Mon, Jun 13, 2016 at 2:12 PM, Mark Millard <markmi@dsl-only.net> = 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E762402-95A9-4A2C-B2CE-B0551E5BBB31>