-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doesn't compile under NixOS #10
Comments
Yeah, there's a lot of hard-coded /bin paths throughout nixpack. (#8 takes a step to fix a few of these, but not all.) We could go fix these more systematically to use some passed path, and theoretically you could point these to an environment with the needed things (sh, coreutils, python, gcc). This would still violate purity, but that's kind of the nature of spack. A more radical option, which I considered initially, is to host nixpack/spack on nixpkgs, so all these needed things are built from nixpkgs automatically, but you'd still need a bootstrap compiler, and using the nix compiler would defeat our purpose for using spack to begin with (i.e., to be able to use system libraries). I suppose the point is that the solution really depends on your use case. Just providing a path and passing that around is probably the simplest solution. |
this has been solved in commit 796e176 |
I see, thanks everyone! |
I did the following:
$ git clone https://github.com/flatironinstitute/nixpack.git $ cd nixpack $ nix-build -A spackRepo /nix/store/w2ll9a0j9g48sklzac68rfgvynxw1qhn-install.sh: line 2: /bin/mkdir: not found
The text was updated successfully, but these errors were encountered: