Skip to content
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

libmolgrid install error #111

Open
croshong opened this issue Mar 29, 2023 · 1 comment
Open

libmolgrid install error #111

croshong opened this issue Mar 29, 2023 · 1 comment

Comments

@croshong
Copy link

I'm trying to install libmolgrid in fresh environment
after typing cmake
when I type make, I got following error

[ 60%] Building CXX object python/CMakeFiles/molgrid.dir/bindings_grids.cpp.o
In file included from /lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/ndarraytypes.h:4,
from /lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/arrayobject.h:5,
from /lwork01/libmolgrid/python/bindings_grids.cpp:18:
/lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/npy_common.h:400:9: error: ‘Py_hash_t’ does not name a type
typedef Py_hash_t npy_hash_t;
^~~~~~~~~
In file included from /lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/arrayobject.h:5,
from /lwork01/libmolgrid/python/bindings_grids.cpp:18:
/lwork01/miniconda3/envs/py39/lib/python3.9/site-packages/numpy/core/include/numpy/ndarraytypes.h:652:9: error: ‘npy_hash_t’ does not name a type; did you mean ‘npy_half’?
npy_hash_t hash;
^~~~~~~~~~
npy_half

the OS environment is following
OS : ubuntu 16.04
gcc : 8.4.0
python : 3.9.16

How can I solve this problem?

@dkoes
Copy link
Contributor

dkoes commented Mar 29, 2023

Python.h should include pyhash.h which defines Py_hash_t. You need to figure out what Python.h is being included instead of the correct one and direct cmake to the correct one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants