Hi, On Wed, 3 Nov 2021 at 00:30, Théo Maxime Tyburn <theo.tyb...@gmail.com> wrote:
> I started using julia in one of my university projects and I am not sure > how this should be done the guix way. Has someone experience with this ? Cool! > For know I just used the julia package manager and the packages are in > ~/.julia. I was not able to use the guix packages for julia > however. Should something be done manually to tell julia where to find > its packages ? For now, it is either packages from Pkg.jl or either packages julia-* from Guix. A patch [1] is still pending for being able to mix both. Aside that packages from Pkg.jl do not always work out-of-the-box, sadly. 1: <http://issues.guix.gnu.org/51319> > I encountered two problems. The first with the package "GR" the > second with the package "GLFW". I encountered these bugs while trying > the packages "Plots" and the "GLMakie" backend of "Makie" IIUC, you installed all the packages using Pkg.jl, right? Because then, I get: --8<---------------cut here---------------start------------->8--- ERROR: could not download https://pkg.julialang.org/registry/23338594-aafe-5451-b93e-139f81909106/302047ed63e49eace1abd20f300ac6e22768690b --8<---------------cut here---------------end--------------->8--- and I do not know if Pkg.jl works correctly with the current julia from Guix. For instance, "guix shell julia -CN -- julia" then 'using Pkg; Pkg.add("Plots")' reports failures. One is reference to build directory "/tmp/guix-build-julia-1.6.2.drv-0", see [2]. 2: <http://issues.guix.gnu.org/issue/48238> > The GR bug: > > julia> using GR > > julia> histogram(randn(10000)) > > env: > > ‘/home/teddd/.julia/artifacts/b5fea2b0d5c84336f26b139587a84ee7e8ca2e12/bin/gksqt’: > > No such file or directory > > connect: Connection refused > > GKS: can't connect to GKS socket application[ > it then exits because of a segmentation fault. Well, I do not know where does the issue come from. I suspect something related to [2] above. For now, I do not have a solution and I do not have time to work on it. Sorry. I would be happy if someone fixes the issue; probably patch#51319 helps here. :-) Cheers, simon
