-
Notifications
You must be signed in to change notification settings - Fork 187
Closed
Description
This has caused some problems for CIBot lately
julia> ENV["PYTHON"]="/usr/bin/python3"
"/usr/bin/python3"
(v1.0) pkg> build PyCall
Building Conda ─→ `~/.julia/packages/Conda/m7vem/deps/build.log`
Building PyCall → `~/.julia/packages/PyCall/rUul9/deps/build.log`
┌ Error: Error building `PyCall`:
│ ERROR: LoadError: Couldn't find libpython; check your PYTHON environment variable.
│
│ The python executable we tried was /usr/bin/python3 (= version3.6);
│ the library names we tried were ["libpython3.6m.so", "libpython3.6m", "libpython3.6", "libpython"]
│ and the library paths we tried were AbstractString["/usr/lib","/usr/lib", "/usr", "/usr/lib"]
│ Stacktrace:
│ [1] error(::String) at ./error.jl:33
│ [2] find_libpython(::String) at /home/andreasnoack/.julia/packages/PyCall/rUul9/deps/build.jl:129
│ [3] top-level scope at logging.jl:313
│ [4] top-level scope at /home/andreasnoack/.julia/packages/PyCall/rUul9/deps/build.jl:196
│ [5] include at ./boot.jl:317 [inlined]
│ [6] include_relative(::Module, ::String) at ./loading.jl:1038
│ [7] include(::Module, ::String) at ./sysimg.jl:29
│ [8] include(::String) at ./client.jl:388
│ [9] top-level scope at none:0
│ in expression starting at /home/andreasnoack/.julia/packages/PyCall/rUul9/deps/build.jl:170
└ @ Pkg.Operations /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.0/Pkg/src/Operations.jl:1068
Metadata
Metadata
Assignees
Labels
No labels