Michael Dusan
Michael Dusan
> using `CMAKE_CONFIGURE_ARGS+= -DCMAKE_INSTALL_PREFIX=${DESTDIR}${PREFIX}` doesn't change a thing in the outcome. > > I'd appreciate pointers in how/where to make zig install in our chroot build environment again. The `CMAKE_INSTALL_PREFIX`...
this looks sus: ``` :: argv[12]: --prefix :: argv[13]: /usr/pkg :: ``` is it possible something stripped the original `--prefix` placement which usually would go at `argv[2]` and appended the...
so in this case, is `--prefix /usr/pkg` correct and the chroot user `pbulk` ? has write access?
are you perhaps on discord or zig's irc?
feel free to ping me. I'm on as freshcoffee in `libera #zig`
Agreed. BTW, it's because global cache is expected to be in home by default. - workaround: `export ZIG_GLOBAL_CACHE_DIR=$PWD`
> > > I also faced to the same situation while compiling master branch or `brew install zig --HEAD` on macOS(x86) zig2 is compiled without problem, but on stage3 kernel...
can you show the output of the following 2 commands, where my_name_exe is what `zig build-exe` produces ``` ldd /usr/bin/env ldd my_main_exe ```
Hmm perhaps the zig executable you are using has a dynamic linker path that is not found on your host. Maybe `ldd` against zig can shed some light.
That looks like it is expecting a dynamic executable and iirc zig shipped in tarballs for linux are static for maximum platform compatibility. But yeah, unrelated.