[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-amd64/54569 (build.sh system seems broken)
Synopsis: build.sh system seems broken
Responsible-Changed-When: Wed, 24 May 2023 11:04:05 +0000
State-Changed-When: Wed, 24 May 2023 11:04:05 +0000
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
and running build.sh from some/src
(those are setenv in tcsh)
and my mk.conf is
(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).
Main Index |
Thread Index |