Re: [igraph] Building universal python-igraph on OSX 10.11

[Jérôme Laheurte]

> Le 10 avr. 2016 à 22:12, Tamas Nepusz <address@hidden> a écrit :
> 
>> Hello. I tried to build a universal version of python-igraph on OS X El 
>> Capitan; it seems that building the C core triggers a clang bug:
> Yes, it's likely that this is the same bug:
> 
> https://llvm.org/bugs/show_bug.cgi?id=27059

Looks like it, yes. But the reporter seems to be using gcc ?

> 
> You could try downgrading to an older version of clang if that is an
> option for you.

Unfortunately not :(

> 
>> I’m using brew because pip does not install the C core…
> It should try to install the C core if it does not find the C core
> already, so maybe you could get around this by removing any installed
> version of the C core first. (If "pkg-config --cflags igraph" does not
> print anything, you should be okay).

As far as I could check (find on various standard library locations for « 
*igraph*dylib* », there wasn’t an older version around.

> 
>> It looks like building with gcc instead of clang should make it work; 
>> unfortunately the —use-gcc option does not seem to have any effect (it still 
>> uses clang). Does anybody have a hint ?
> Just a hint, but on my machine, gcc is symlinked to clang:
> 
>> /usr/bin/gcc -v
> Configured with:
> --prefix=/Applications/Xcode.app/Contents/Developer/usr
> --with-gxx-include-dir=/usr/include/c++/4.2.1
> Apple LLVM version 6.0 (clang-600.0.51) (based on LLVM 3.5svn)
> Target: x86_64-apple-darwin13.4.0
> Thread model: posix
> 
> So it could be the case that you don't have a "real" gcc on your
> machine. Try installing a homebrewed gcc.

I forgot to tell, I already had homebrewed gcc. But « gcc —version » still 
gives me the Xcode symlink to clang… I’ll try setting explicitely CC or 
whatever home-brew uses.

Thanks
Jérôme Laheurte

signature.asc
Description: Message signed with OpenPGP using GPGMail