-
-
Notifications
You must be signed in to change notification settings - Fork 25
PyError: 'pkg-config is not installed' #52
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
Comments
I've not updated the package to work for 1.0 but will hopefully do this by the weekend. If I'm not mistaken though, this seems to be a Conda Issue. |
I see. I'll downgrade to 0.7. |
Confirmed same issue on 0.7. |
Confirmed same issue on 0.6.2. I'd like to at minimum get a working FEniCS installation again - if this is a Conda issue, can I do anything to debug it? |
Julia 1.0, FEniCS.jl master, miniconda 4.5.10 and FEniCS 2018.1 works for me (linux x86_64). Are you sure you have set |
Aha, found the culprit! Whenever PyCall rebuilds (e.g., after an update), it resets to the default ENV["PYTHON"]=""
using Pkg; Pkg.build("PyCall") and then restart julia. |
@aterenin Have you installed
(even though both |
No - I have never gotten mshr to work with FEniCS.jl, and learned from previous versions that attempting this on Mac was unwise.
My configuration is 100% default - on Mac run ‘rm -rf ~/.julia’, then launch Julia and run ‘Pkg.add(“FEniCS.jl”)’ with no other steps of any kind.
On Aug 22, 2018, at 11:43 PM, Christian Clason <notifications@github.com<mailto:notifications@github.com>> wrote:
@aterenin<https://github.com/aterenin> Have you installed mshr by any chance? I can reproduce the problem if I install mshr. Curiously, it will say
The following packages will be UPDATED:
fenics: 2016.1.0-py35_1 conda-forge --> 2018.1.0-py35he4728cc_0 conda-forge
The following packages will be DOWNGRADED:
numpy: 1.15.1-py35_blas_openblashd3ea46f_0 conda-forge [blas_openblas] --> 1.14.5-py35_blas_openblashd3ea46f_201 conda-forge [blas_openblas]
(even though both Conda.list() shows the correct fenics version before that, looking at fenics.DOLFIN_VERSION_STRING shows that it was actually installing 2016.1.0). So something is definitely screwy with Conda.jl, at least on macOS. You might want to open an issue; in the meantime, I recommend installing FEniCS via an external miniconda installation and accessing this. (Don't forget to Pkg.build(PyCall) with the correct environment activated!)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#52 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEgPKGSiZSZsvtvU0JLJJ5DII5x6OPvaks5uTcJpgaJpZM4V8bte>.
|
@aterenin Since
]add Conda
using Conda
Conda.add("sympy=1.1") # and matplotlib and scipy, if desired
ENV["PYTHON"]=""
using Pkg; Pkg.build("PyCall")
using PyCall
@pyimport fenics as fe # :smile:
fe.DOLFIN_VERSION_STRING # :sadface:
The only possible conclusion is that FEniCS from Conda.jl has to be assumed to be broken at the moment on macOS. On the other hand, direct install via miniconda does work, so that would be my recommended workaround (and actually standard way):
conda create -n fenics -c conda-forge fenics sympy=1.1 matplotlib scipy mshr Grab a cup of tea.
import dolfin as fe
fe.__version__
ENV["PYTHON"]="python3"
using Pkg; Pkg.build("PyCall")
using PyCall
@pyimport dolfin as fe
fe.__version__
mesh = fe.UnitSquareMesh(64,64)
V = fe.FunctionSpace(mesh,"CG",1) # should trigger FFC compilation
Again, whenever PyCall.jl gets updated, make sure you repeat step 6 with If this works for you, maybe @ysimillides or @ChrisRackauckas can put these instructions (which also work for linux) in the README or the Wiki. |
Fresh installation of Julia 1.0.
What can I do to debug this?
The text was updated successfully, but these errors were encountered: