11 ms·
You could run the build process with chroot or inside Docker, so that the hardcoded paths actually resolve to a designated subdirectory.
by scribu 1y ago
You could run the build process with chroot or inside Docker, so that the hardcoded paths actually resolve to a designated subdirectory.
- mananaysiempre 1y agoIncidentally, that’s what is usually done in Nixpkgs in similar situations when there’s no better alternative, see buildFHSEnv et al.
- akdev1l 1y agoIn many cases the build output also has hardcoded paths unfortunately so doing `brew install` inside a container with the proper volumes it’s not sufficient to fix the issue. Everything would have to run from within the container as well.