Hi Henri,
This sounds a bit like you don't have `make` in your PATH? You can check if
Sundials was downloaded and unpacked into
~/.julia/v0.3/src/sundials-2.5.0/. In that directory you can manually run
`make install`. If that works you might be able to run
`Pkg.build("Sundials")` again. If you still have problems it might be good
to create an issue for Sundials.jl
<https://github.com/JuliaLang/Sundials.jl/issues>.
Best,
Alex.
On Thursday, 21 May 2015 12:52:32 UTC+2, Henri Laurie wrote:
>
> Sorry for the tone, screaming loudly here despite sore throat, because
>
> --- I was very happy when Debian Jessie became the stable distribution,
> because I could then simply install julia. I particularly want to use the
> Sundials and PyPlot packages, for preference running most of it in the
> IJulia notebook interface.
>
> --- This worked fine on my laptop (don't have it here, it's an oldish
> low-spec Lenovo)
>
> --- So put Jessie on my desktop, installed julia. No problem. Installed
> IJulia, no problem (though I don't like the inelegant shutting down, have
> to kill ipython separately, it's the same on the laptop).
>
> --- BUT I can't install Sundials. I get (skipping a lot of messages that
> all seem to indicate the process is going fine)
>
> """
> ...
>
> ----------------------------------
> Finished SUNDIALS Configure Script
> ----------------------------------
>
> INFO: Changing Directory to
> /home/henri/.julia/v0.3/Sundials/deps/src/sundials-2.5.0
> ==============================[ ERROR: Sundials
> ]===============================
>
> could not spawn `make install`: no such file or directory (ENOENT)
> while loading /home/henri/.julia/v0.3/Sundials/deps/build.jl, in
> expression starting on line 37
>
> ...
> """
>
> and skipping a short summary in the tail.
>
> I can't work out where the problem might be. Thought it might be that I
> didn't have fortran or other compilers, so by overkill I installed
> everything I could find in my Jessie distribution, deleted julia with
> Pkg.rm and also by removing all of .julia in my home directory. Didn't
> help. BTW this fixed PyPlot which at first would build and give no error
> when running "using PyPlot" but then would say in response to a "plot"
> command that pltm could not be found.
>
