Closed smaret closed 6 years ago
It seems that the python interpreter and package is in the nativeBuildInputs
(https://github.com/Gricad/nix-ciment-channel/blob/master/ciment/gildas/default.nix#L15) which means that they are not used at run time. They should be in the buildInputs
so they are available at run time. (Or maybe PropagatedbuildInputs
I'm not sure...)
Thanks @mickours. I tried both buildInputs
and PropagatedBuildInputs
, but I still get the error.
Ok my bad I didn't understand the real problem. I though that you tool was in python but it is executing a Python interpreter at runtime.
It seems that your tool is looking inside the system python installation /usr/lib/python2.7
and not the in the PATH. Maybe you have some hard-coded path in your code that you have to patch.
Are you sure? It works fine if I install python2.7
and numpy
with nix-env
.
To clarify my comment above: a quick fit is to create a python27-env.nix
file containing the following lines:
with import <nixpkgs> {};
pkgs.python27.withPackages (ps: with ps; [ numpy ])
and then install python
and numpy
it in a profile with nix-env -i -f python27-env.nix
. This allows gildas
to find the correct python
version (which means that the path is not hardcoded in gildas
).
Ideally, this should be done in Gildas' nix
package.
I get the following error when I try to start a
python
interpreter withingildas
:It looks like
gildas
peaks the system library instead ofnix
's one. Allgildas
versions seems to be affected by this bug (I rolled back todec17a
, but the bug is present in newer versions too).