Date: Mon, 13 Jun 2016 14:12:54 -0700 From: Mark Millard <markmi@dsl-only.net> To: Bryan Drewery <bdrewery@FreeBSD.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: WITH_META_MODE vs. delete-old and delete-old-libs Message-ID: <31063879-DF43-4895-A9EA-99A70DCFE4A1@dsl-only.net>
next in thread | raw e-mail | index | archive | help
I've been using the following script to run my make commands for amd64 = builds (as an example): > # more = ~/sys_build_scripts.amd64-host/make_amd64_nodebug_clang_bootstrap-amd64-ho= st.sh=20 > 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 $* 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. Without WITH_META_MODE=3D each prompt text is displayed before it waits = for the answer to that prompt. 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? =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?31063879-DF43-4895-A9EA-99A70DCFE4A1>