igraph problem on Lion
ryandesign at macports.org
Tue Nov 1 00:30:58 PDT 2011
On Oct 31, 2011, at 22:31, Wu Degang wrote:
> I was trying to build igraph 0.5.4 on Lion but failed. The following is the error message in the terminal:
> Error: Target org.macports.build returned: shell command failed (see log for details)
> Error: Failed to install igraph
> Log for igraph is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_igraph/igraph/main.log
> The following is the relevant (I think) section in the log file:
> :info:build libtool: compile: /Developer/usr/bin/llvm-g++-4.2 -DHAVE_CONFIG_H -I. -I.. -pipe -O2 -arch x86_64 -I/opt/local/include/libxml2 -pipe -O2 -arch x86_64 -MT libigraph_la-gengraph_box_list.lo -MD -MP -MF .deps/libigraph_la-gengraph_box_list.Tpo -c gengraph_box_list.cpp -o libigraph_la-gengraph_box_list.o >/dev/null 2>&1
> :info:build DensityGrid.cpp: In member function ‘float drl::DensityGrid::GetDensity(float, float, bool)’:
> :info:build DensityGrid.cpp:76: internal compiler error: Segmentation fault: 11
It sounds like igraph does not like to be compiled with llvm-gcc-4.2 or clang. I get the same error on Snow Leopard with Xcode 3.2.6 if I do:
sudo port install igraph configure.compiler=llvm-gcc-4.2
sudo port install igraph configure.compiler=clang
It compiles fine for me with gcc-4.2.
This is the kind of thing you should usually file a bug report in our issue tracker for.
> :info:build Please submit a full bug report,
> :info:build with preprocessed source if appropriate.
> :info:build See <URL:http://developer.apple.com/bugreporter> for instructions.
Ordinarily I would suggest you do this, except in this case it looks like somebody has already done so:
You can probably work around the problem with:
sudo port install igraph configure.compiler=gcc-4.2
Or, if you are using Xcode 4.2+, which does not include gcc anymore, do:
sudo port install apple-gcc42
sudo port install igraph configure.compiler=apple-gcc-4.2 configure.cxx=/opt/local/bin/gcc-apple-4.2
This is the workaround suggested in the above thread.
Also there is a patch:
More information about the macports-users