After successfully using the likes of: env MAKEOBJDIRPREFIX=. . . make . . . from the usual /usr/src starting point. I tried following: > The environment of make(1) for the build can be controlled via the > SRC_ENV_CONF variable, which defaults to /etc/src-env.conf. Some > examples that may only be set in this file are MAKEOBJDIRPREFIX, > WITH_DIRDEPS_BUILD, and WITH_META_MODE as they are environment-only > variables. by using env SRC_ENV_CONF=. . . make . . . and having the file pointed to contain the MAKEOBJDIRPREFIX=. . . . This did not work. Say MAKEOBJDIRPREFIX=/usr/obj/xtoolchain then I'd get errors for the likes of /usr/obj/xtoolchain/legacy/usr/lib/ not existing during an install operation during buildworld. If I forced a such legacy directory tree to exist there by copying the empty tree from /usr/obj/xtoolchain/usr/src/tmp/legacy/. . . (that it had created) I continued to have problems elsewhere, such as: --- _libinstall --- sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libctf.a /usr/obj/xtoolchain/usr/lib/ install: /usr/obj/xtoolchain/usr/lib/: No such file or directory *** [_libinstall] Error code 71 In essence the dynamic, local additions to the path such as usr/src/tmp/ sometimes end up missing. My guess is that it is picking up the MAKEOBJDIRPREFIX=/usr/obj/xtoolchain definition again and so replacing the built-up prefix for the local context. May be the quoted paragraph from "man src.conf" should not suggest that MAKEOBJDIRPREFIX is valid in a file to be referenced by SRC_ENV_CONF: > The environment of make(1) for the build can be controlled via the > SRC_ENV_CONF variable, which defaults to /etc/src-env.conf. Some > examples that may only be set in this file are MAKEOBJDIRPREFIX, > WITH_DIRDEPS_BUILD, and WITH_META_MODE as they are environment-only > variables. === Mark Millard markmi at dsl-only.netReceived on Sun Dec 06 2015 - 14:21:28 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:01 UTC