Thanks!
However, I'm having trouble with it :-C. This might be entirely due to our
setup, in which we're installing on a server that we don't have admin
control over. This has previously caused issues with libraries being
compiled with/without options that igraph doesn't expect, but my
understanding was that the newer versions of python-igraph had resolved
this issue.
Notably, we get different errors depending on whether we use pip or just
clone the 0.7 branch of python-igraph from github.
pip install:
src/arpackobject.c:133: error: for each function it appears in.)
src/arpackobject.c:133: error: expected ';' before 'n'
src/arpackobject.c:144: error: 'igraphmodule_ARPACKOptionsObject' has no
member named 'params'
src/arpackobject.c:144: error: 'igraph_real_t' undeclared (first use in
this function)
src/arpackobject.c:144: error: expected ';' before 'PyLong_AsLong'
src/arpackobject.c:146: error: 'igraphmodule_ARPACKOptionsObject' has no
member named 'params'
src/arpackobject.c:146: error: expected ';' before 'PyFloat_AsDouble'
src/arpackobject.c: At top level:
src/arpackobject.c:160: error: expected '=', ',', ';', 'asm' or
'__attribute__' before '*' token
error: command 'gcc' failed with exit status 1
----------------------------------------
Cleaning up...
Command /home/bowen_yan/anaconda3/bin/python3 -c "import setuptools,
tokenize;__file__='/tmp/pip_build_bowen_yan/python-igraph/se
tup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" install --record /tmp/pip-rmcw1fbs-record/install-record.txt
--single-version-externally-managed --compile failed with error code 1
in /tmp/pip_build_bowen_yan/python-igraph
Storing debug log for failure in /home/bowen_yan/.pip/pip.log
python setup.py install:
gcc -pthread -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC
-Iigraphcore/include -I../../build/include -I../../include
-I/usr/local/include/igraph -I/usr/include/igraph
-I/home/bowen_yan/anaconda3/include/python3.4m -c src/pyhelpers.c -o
build/temp.linux-x86_64-3.4/src/pyhelpers.o
gcc -pthread -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC
-Iigraphcore/include -I../../build/include -I../../include
-I/usr/local/include/igraph -I/usr/include/igraph
-I/home/bowen_yan/anaconda3/include/python3.4m -c src/arpackobject.c -o
build/temp.linux-x86_64-3.4/src/arpackobject.o
gcc -pthread -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC
-Iigraphcore/include -I../../build/include -I../../include
-I/usr/local/include/igraph -I/usr/include/igraph
-I/home/bowen_yan/anaconda3/include/python3.4m -c src/indexing.c -o
build/temp.linux-x86_64-3.4/src/indexing.o
In file included from src/indexing.c:25:
src/convert.h:63: error: expected declaration specifiers or '...' before
'igraph_layout_grid_t'
src/convert.h:66: error: expected declaration specifiers or '...' before
'igraph_random_walk_stuck_t'
error: command 'gcc' failed with exit status 1
On Mon, Feb 9, 2015 at 11:48 PM, Tamas Nepusz <[email protected]> wrote:
> For the record: python-igraph 0.7.1 is now out there on PyPI:
>
> https://pypi.python.org/pypi/python-igraph
>
> I still need to create installers for Windows, although I'm not sure when
> I will find time to do that.
>
> --
> T.
>
> On 01/28, Jeff Alstott wrote:
> > Well, I hacked cairocffi into the 0.7 branch of python-graph. But now it
> > turns out I would really rather use the development version, due to this
> > (now fixed) problem plotting in Ipython Notebooks on Python 3:
> >
> http://stackoverflow.com/questions/26887513/igraph-plot-function-does-not-show-images-in-an-ipython-notebook
> >
> > But I can't actually make the development igraph still. I built flex from
> > source, then:
> > ./configure --prefix=${HOME}
> > make
> > make check
> >
> > This is what I get at the end of make check:
> >
> > make[2]: Leaving directory `/home/jeffrey_alstott/igraph/src'
> > make[1]: Leaving directory `/home/jeffrey_alstott/igraph/src'
> > Making check in tests
> > make[1]: Entering directory `/home/jeffrey_alstott/igraph/tests'
> > make check-local
> > make[2]: Entering directory `/home/jeffrey_alstott/igraph/tests'
> > { \
> > echo '# Signature of the current package.'; \
> > echo 'm4_define([AT_PACKAGE_NAME], [igraph])'; \
> > echo 'm4_define([AT_PACKAGE_TARNAME], [igraph])'; \
> > echo 'm4_define([AT_PACKAGE_VERSION],
> > [0.8.0-pre+594.701edd8])'; \
> > echo 'm4_define([AT_PACKAGE_STRING], [igraph
> > 0.8.0-pre+594.701edd8])'; \
> > echo 'm4_define([AT_PACKAGE_BUGREPORT], [
> [email protected]])';
> > \
> > } >./package.m4
> > /bin/sh /home/jeffrey_alstott/igraph/missing --run autom4te
> > --language=autotest -I ../tests ../tests/testsuite.at -o testsuite.tmp
> > /usr/bin/m4:community.at:58: ERROR: end of file in argument list
> > autom4te: /usr/bin/m4 failed with exit status: 1
> > make[2]: *** [testsuite] Error 1
> > make[2]: Leaving directory `/home/jeffrey_alstott/igraph/tests'
> > make[1]: *** [check-am] Error 2
> > make[1]: Leaving directory `/home/jeffrey_alstott/igraph/tests'
> > make: *** [check-recursive] Error 1
> >
> > On Wed, Jan 28, 2015 at 10:29 AM, Jeff Alstott <[email protected]>
> > wrote:
> >
> > > Thanks for the info to you both!
> > >
> > > I now need to decide if I should set up the development branch on my
> > > machine, or hack my python-igraph to allow for cairocffi. Which is
> likely a
> > > better move? Possible considerations:
> > > - How stable is the development branch right now?
> > > - Is there any estimate of when the next version will be released?
> (with
> > > cairocffi presumably baked in)
> > > - Is either move likely to cause me any other problems down the line?
> > >
> > > On Tue, Jan 27, 2015 at 3:35 PM, Jeff Alstott <[email protected]>
> > > wrote:
> > >
> > >> I am trying to build and install the development version of igraph and
> > >> python-igraph, because I want to use cairocffi instead of pycairo
> (which
> > >> has been implemented in the development, but not version 0.7).
> However, I'm
> > >> having trouble configuring igraph:
> > >>
> > >> $ls
> > >> AUTHORS configure.ac debian igraph_Info.plist.in
> > >> INSTALL.WINDOWS msvc optional tests
> > >> bootstrap.sh CONTRIBUTING.md doc igraph.pc.in
> > >> interfaces NEWS README TODO
> > >> ChangeLog COPYING examples include
> > >> Makefile.am nexus src tools
> > >>
> > >>
> > >> $./configure
> > >> bash: ./configure: No such file or directory
> > >>
> > >> $chmod +x configure.ac
> > >>
> > >> $./configure.ac
> > >> ./configure.ac: line 1: syntax error near unexpected token `igraph,'
> > >> ./configure.ac: line 1: `AC_INIT(igraph, esyscmd([tr -d '\n' <
> > >> VERSION]), [email protected])'
> > >>
> > >>
> > >> What am I missing?
> > >>
> > >>
> > >
>
> > _______________________________________________
> > igraph-help mailing list
> > [email protected]
> > https://lists.nongnu.org/mailman/listinfo/igraph-help
>
>
> --
> T.
>
> _______________________________________________
> igraph-help mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/igraph-help
>
_______________________________________________
igraph-help mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/igraph-help
