Skip to content
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

Closed
Qubasa opened this issue Jan 13, 2022 · 3 comments
Closed

Doesn't compile under NixOS #10

Qubasa opened this issue Jan 13, 2022 · 3 comments

Comments

@Qubasa
Copy link

Qubasa commented Jan 13, 2022

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
$ nix-info   
system: "x86_64-linux", multi-user?: yes, version: nix-env (Nix) 2.4, channels(mjnam): "", channels(harshanavkis): "home-manager-21.05", channels(root): "nix-ld, nixos-21.05.4448.4a8751d694b", nixpkgs: /nix/store/8hd2049cr4dz9myjcjjh6cjjapz1p107-source
@dylex
Copy link
Member

dylex commented Jan 13, 2022

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.

@dguibert
Copy link
Contributor

this has been solved in commit 796e176

@Qubasa
Copy link
Author

Qubasa commented Jan 16, 2022

I see, thanks everyone!

@Qubasa Qubasa closed this as completed Jan 16, 2022
dylex added a commit that referenced this issue Jan 16, 2022
based in part on #8 and addressing part of #10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants