[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[igraph] Help installing Python-igraph

From: Evan Driscoll
Subject: [igraph] Help installing Python-igraph
Date: Fri, 10 Aug 2012 15:42:35 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20110414 Thunderbird/3.1.10


I'm on a 64-bit RHEL5 (/6) machine and am having trouble installing the Python bindings. Any ideas of what I'm doing wrong and how to fix it would be appreciated.

I have igraph itself installed at a prefix of /unsup/igraph-0.6/$(sys), and I do the following to try to get Python working:

    mkdir -p /unsup/igraph-0.6/$(sys)/lib/python2.7/site-packages/
    export PYTHONPATH=/unsup/igraph-0.6/$(sys)/lib/python2.7/site-packages/
    export PKG_CONFIG_PATH=/unsup/igraph-0.6/$(sys)/lib/pkgconfig
    export LD_LIBRARY_PATH=/unsup/igraph-0.6/$(sys)/lib

    python setup.py install --prefix=/unsup/igraph-0.6/$(sys)

(The command $(sys) expands to either 'amd64_rhel5' or 'amd64_rhel6'.)

However, when I try to 'import igraph', it says it can't find module '_igraph'. Furthermore, if I look into the site-packages directory named above, it's emptyish:

    $ tree /unsup/igraph-0.6/$(sys)/lib/python2.7/site-packages
    |-- easy-install.pth
    |-- python_igraph-0.6-py2.7-linux-x86_64.egg
    |-- site.py
    `-- site.pyc
    0 directories, 4 files

This is the case on both RHEL5 and 6.

Interestingly, 32-bit RHEL5 does more:
    $ tree /unsup/igraph-0.6/i386_rhel5/lib/python2.7/site-packages
    |-- igraph
    |   |-- __init__.py
    |   |-- __init__.pyc
    |   |-- _igraph.so
    |   |-- app
    |   |   |-- __init__.py
    5 directories, 106 files

but it still complains that it can't find the _igraph module. (I have PYTHONPATH=/unsup/igraph-0.6/i386_rhel5/lib/python2.7/site-packages and LD_LIBRARY_PATH=/unsup/igraph-0.6/i386_rhel5/lib/.)

Finally, there are _igraph.so files under build/ in the source tree (and as you can see above, that's present in

I admit that this setup is a bit strange, and it could very easily be picking up the wrong Python when doing compilation or something, though I haven't had much problems installing Python modules in the past.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]