igraph-help
[Top][All Lists]
Advanced

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

Re: [igraph] Installing python-igraph on MAC OS X (tiger)


From: Tamas Nepusz
Subject: Re: [igraph] Installing python-igraph on MAC OS X (tiger)
Date: Thu, 11 Dec 2008 10:56:19 +0000

Hi Alessandro,

> Thanks a lot for your attention, and sorry for the late reply.
> 
> Unfortunately the problem is still there.
> 
> Any other idea about the reason of the problem?
Can you please send me your modified setup.py file? It seems like
despite you have specified /usr/lib in LIBIGRAPH_FALLBACK_LIBRARY_DIRS,
the compiler still tries to link with /usr/local/lib as the library
path. Also, can you send me the output of the following command (if it's
an error message, then the error message):

pkg-config igraph --libs --cflags

-- 
Tamas


On Thu, 2008-12-11 at 11:43 +0100, Alessandro Antonucci wrote:
> Hi Tamas!
> 

> Let me try to report all the relevant information.
> 
> - the testsuit of igraph works well
> 
> - libigraph.dylib is in /usr/lib/
> 
> - this file is the only 'libigraph.dylib' file in my system
> 
> -  The command file libigraph.dylib
> properly returns: libigraph.dylib: Mach-O dynamically linked shared
> library i386
> 
> - In the setup.py file, I've specified '/usr/lib' both in
> LIBIGRAPH_FALLBACK_LIBRARY_DIRS and LIBIGRAPH_FALLBACK_INCLUDE_DIRS 
> 
> Nevertheless, I've still the same problem, as the output of:
> 
> sudo python setup.py build
> 
> is still:
> 
> Include path: /usr/local/include/igraph
> Library path: /usr/local/lib
> running build
> running build_py
> running build_ext
> building 'igraph.core' extension
> gcc -arch i386 -arch ppc -isysroot /Developer/SDKs/MacOSX10.4u.sdk -g
> -bundle -undefined dynamic_lookup
> build/temp.macosx-10.3-i386-2.5/src/arpackobject.o
> build/temp.macosx-10.3-i386-2.5/src/bfsiter.o
> build/temp.macosx-10.3-i386-2.5/src/common.o
> build/temp.macosx-10.3-i386-2.5/src/convert.o
> build/temp.macosx-10.3-i386-2.5/src/edgeobject.o
> build/temp.macosx-10.3-i386-2.5/src/edgeseqobject.o
> build/temp.macosx-10.3-i386-2.5/src/error.o
> build/temp.macosx-10.3-i386-2.5/src/graphobject.o
> build/temp.macosx-10.3-i386-2.5/src/igraphmodule.o
> build/temp.macosx-10.3-i386-2.5/src/vertexobject.o
> build/temp.macosx-10.3-i386-2.5/src/vertexseqobject.o -L/usr/local/lib
> -ligraph -o build/lib.macosx-10.3-i386-2.5/igraph/core.so
> /usr/bin/ld: for architecture i386
> /usr/bin/ld: can't locate file for: -ligraph
> /usr/bin/ld: for architecture ppc
> /usr/bin/ld: can't locate file for: -ligraph
> collect2: ld returned 1 exit status
> collect2: ld returned 1 exit status
> lipo: can't open input file: /var/tmp//ccjWigyQ.out (No such file or
> directory)
> error: command 'gcc' failed with exit status 1
> 
> 
> 2008/12/4 Tamas Nepusz <address@hidden>
>         Hi Alessandro,
>         
>         Do you happen to have another copy of libigraph.dylib
>         in /usr/local/lib? (E.g., from a previous try when you tried
>         to install the Leopard package). If so, please move all
>         igraph-related files and directories from /usr/local/lib
>         and /usr/local/include to another temporary directory as it
>         may confuse the linker.
>         
>         -- 
>         Tamas
>         
>         
>         
>         On 2008.12.04., at 13:19, address@hidden
>         wrote:
>         
>                 > Can you please check the architecture of that file
>                 by "file /usr/lib/libigraph.dylib"? It should be
>                 "libigraph.dylib: Mach-O dynamically linked shared
>                 library i386" if you are using an Intel-based Mac.
>                 
>                 It is like that.
>                 
>                 In fact the output of:
>                 
>                 $ file libigraph.dylib
>                 
>                 is exactly:
>                 
>                 > libigraph.dylib: Mach-O dynamically linked shared
>                 library i386
>                 
>                 Thanks a lot for your support.
>                 
>                 Alessandro
>         
>         
> 





reply via email to

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