Open nikkicoon opened 1 month ago
It looks like you are compiling zig from source. Have you tried changing the global cache directory? https://github.com/ziglang/zig/issues/19400#issuecomment-2016282007
I should mention this is for pkgsrc, a package manager.
the global cache directory is changed from any default to control files: http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/lang/zig/Makefile?rev=1.41&content-type=text/x-cvsweb-markup
MAKE_ENV+= ZIG_GLOBAL_CACHE_DIR=${WRKDIR}/zig-global-cache MAKE_ENV+= ZIG_LOCAL_CACHE_DIR=${WRKDIR}/zig-local-cache
where WRKDIR is the directory pkgsrc builds in
"expected to be found in $HOME by default" I understand this as you can change it, as seen in other package managers unless that changed in recent versions.
This happens when you run it inside the pbulk chroot. It does not happen (ie it installs successfully) when you run it as a user outside of the chroot.
Or are you telling me that stage3 is special, it ignores any previous cache files from stage1 and stage2 if any exist, and when $HOME does not exist, it just fails to complete stage3 install? Your own CI scripts do the same.
I think a good first step here would be obtaining an error return trace, and using that to improve the error reporting instead of just printing "access denied" with no other information.
do you need more verbose cmake output then?
I should mention this is for pkgsrc, a package manager.
the global cache directory is changed from any default to control files: http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/lang/zig/Makefile?rev=1.41&content-type=text/x-cvsweb-markup
MAKE_ENV+= ZIG_GLOBAL_CACHE_DIR=${WRKDIR}/zig-global-cache MAKE_ENV+= ZIG_LOCAL_CACHE_DIR=${WRKDIR}/zig-local-cache
where WRKDIR is the directory pkgsrc builds in
"expected to be found in $HOME by default" I understand this as you can change it, as seen in other package managers unless that changed in recent versions.
This happens when you run it inside the pbulk chroot. It does not happen (ie it installs successfully) when you run it as a user outside of the chroot.
Worth mentioning: this happens regardless of ZIG_(GLOBAL,LOCAL)_CACHE_DIR being set to a different location or not, I just verified this.
Zig Version
0.13.0
Steps to Reproduce and Observed Behavior
I think I reported this before... zig fails to install since at least 0.12.0. This is 0.13.0, on NetBSD, but should be reproducible on any other OS through pkgsrc:
Expected Behavior
zig installs.