Re: port-amd64/54569 (build.sh system seems broken)

[lukem%NetBSD.org@localhost]

Synopsis: build.sh system seems broken

Responsible-Changed-From-To: port-amd64-maintainer->lukem
Responsible-Changed-By: lukem%NetBSD.org@localhost
Responsible-Changed-When: Wed, 24 May 2023 11:04:05 +0000
Responsible-Changed-Why:


State-Changed-From-To: open->feedback
State-Changed-By: lukem%NetBSD.org@localhost
State-Changed-When: Wed, 24 May 2023 11:04:05 +0000
State-Changed-Why:

Is this still a problem?
Your mk.conf in the description doesn't appear to be a valid text file.

build.sh as a tool definitely works; I've built multiple builds of -current
for target amd64 on hosts NetBSD/amd64 and macOS/arm64, unprivileged, in
source and obj in my home dir.

For your build, a couple of features to suggestion:
- use build.sh -U or  mk.conf MKUNPRIVED=yes
- build.sh -u (MKUPDATE=yes) definitely works as advertised;
  I use that in my mk.conf all the time

My build environment is involves setting
   env MAKEOBJDIRPREFIX=some/obj
   env TOOLDIR=some/tool
   env MAKECONF=some/src/mk.conf
and running build.sh from some/src
(those are setenv in tcsh)
and my mk.conf is
MAKEVERBOSE=1
MKUNPRIVED=yes
MKUPDATE=yes
(all of which can be provided to build.sh CLI)

Arguably -U (MKUNPRIVED=yes) should be the default (see PR 42088)
and the N variations of OBJDIR handling could be cleaned up (out of scope
of this PR).