> 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 You could try downgrading to an older version of clang if that is an option for you. > 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). > 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. Best, T. _______________________________________________ igraph-help mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/igraph-help
