Hi, I can't get past the ./configure because it can't find boost, but I installed boost under /usr/local/boost... where does it look for boost? -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi Janna, On 05/12/2011 12:45 AM, Janna wrote:
I can't get past the ./configure because it can't find boost, but I installed boost under /usr/local/boost... where does it look for boost?
The default is usually in /usr, not /usr/local. But you can specify the boost root path with the --with-boost option. Note that if you installed libraries outside the usual paths, you have to tell the linker where to find them, by setting the LDFLAGS variable. In your case you would do ./configure --with-boost=/usr/local/boost LDFLAGS="-l/usr/local/boost/lib" (I am assuming the compiled libraries reside in /usr/local/boost/lib, you have to verify if it is the case) Take a look at "./configure --help" for the many other options you can use. Cheers, Tiago
-- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com. _______________________________________________ graph-tool mailing list graph-tool@skewed.de http://lists.skewed.de/mailman/listinfo/graph-tool
-- Tiago de Paula Peixoto <tiago@skewed.de>
Hi, I got boost going and I pointed graph-tool to it but it still can't find it. I'm using the EPD python distribution and it installs in a non-standard location- this is what I put in sudo ./configure --with-boost=/Library/Frameworks/EPD64.framework/Versions/7.0/lib/boost LDFLAGS="-L/Library/Frameworks/EPD64.framework/Versions/7.0/lib -L/Library/Frameworks/EPD64.framework/Versions/7.0/lib/boost/libs" It finds python but it still spits this out: checking for boostlib >= 1.38.0... configure: error: We could not detect the boost libraries (version 1.38 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation. Thanks for your help. -Janna -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi Janna, On 05/14/2011 01:12 AM, Janna wrote:
Hi,
I got boost going and I pointed graph-tool to it but it still can't find it. I'm using the EPD python distribution and it installs in a non-standard location- this is what I put in
sudo ./configure --with-boost=/Library/Frameworks/EPD64.framework/Versions/7.0/lib/boost LDFLAGS="-L/Library/Frameworks/EPD64.framework/Versions/7.0/lib -L/Library/Frameworks/EPD64.framework/Versions/7.0/lib/boost/libs"
It finds python but it still spits this out:
checking for boostlib >= 1.38.0... configure: error: We could not detect the boost libraries (version 1.38 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in <boost/version.hpp>. See http://randspringer.de/boost for more documentation.
You have to pass configure the path it wants, which depends on how boost was installed. I'm unfamiliar with how EDP installs boost, but you should take a look at config.log, and see why the tests are failing. From this it is usually possible to understand which path you should be passing. Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>
Hi, I sent you an email with the log files, but I went through and tried to install with macports- everything went through fine except for graph-tool. I ran it with sudo ./configure --with-boost-python=/opt/local/var/macports/software/boost/1.46.1_0/opt/local/include/boost/python/ LDFLAGS="-l/opt/local/var/macports/software/boost/1.46.1_0/opt/local/include/boost/python/" LDFLAGS="-L/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib" and it gave me checking for boostlib >= 1.38.0... yes checking whether the Boost::Python library is available... no configure: error: No usable boost::python found I don't know where else to point it to- it's now got the standard python installation and standard boost installation, I checked and that seems to be where the boost python libraries are. Thanks for your help -Janna -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi Janna, On 05/16/2011 07:13 PM, Janna wrote:
Hi,
I sent you an email with the log files, but I went through and tried to install with macports- everything went through fine except for graph-tool. I ran it with
sudo ./configure --with-boost-python=/opt/local/var/macports/software/boost/1.46.1_0/opt/local/include/boost/python/ LDFLAGS="-l/opt/local/var/macports/software/boost/1.46.1_0/opt/local/include/boost/python/" LDFLAGS="-L/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib"
Note that you should pass the _name_ or _suffix_ of the boost python library to the --with-boost-python option, not the include path.
and it gave me
checking for boostlib >= 1.38.0... yes checking whether the Boost::Python library is available... no configure: error: No usable boost::python found
I don't know where else to point it to- it's now got the standard python installation and standard boost installation, I checked and that seems to be where the boost python libraries are. Thanks for your help -Janna
I've looked at your log file, and the error is something like: configure:17268: checking for exit in -lboost_python-mt-py2.5 configure:17293: /usr/bin/g++-4.2 -o conftest -pipe -O2 -arch x86_64 -Wall -ftemplate-depth-150 -Wno-deprecated -O99 -fvisibility=default -fvisibility-inlines-hidden -fopenmp -I/opt/local/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -L/opt/local/lib -arch x86_64 -L/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 -lpython2.7 conftest.cpp -lboost_python-mt-py2.5 >&5 ld: library not found for -lboost_python-mt-py2.5 collect2: ld returned 1 exit status Which means the configure script is not being able to figure out how the boost_python library is called. It tries some common variants, but there is no universal method of identifying it. Could you check under what name is the boost_python library installed? You should pass either the correct full name or suffix to the --with-boost-python option. This is strange, because for me the standard macports name is recognized just fine. Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>
Hi, I went through it again and this is what I get for the boost/python location: /opt/local/include/boost/python /opt/local/include/boost/python/arg_from_python.hpp /opt/local/include/boost/python/args.hpp /opt/local/include/boost/python/args_fwd.hpp /opt/local/include/boost/python/back_reference.hpp /opt/local/include/boost/python/base_type_traits.hpp /opt/local/include/boost/python/bases.hpp /opt/local/include/boost/python/borrowed.hpp /opt/local/include/boost/python/call.hpp /opt/local/include/boost/python/call_method.hpp /opt/local/include/boost/python/cast.hpp /opt/local/include/boost/python/class.hpp /opt/local/include/boost/python/class_fwd.hpp /opt/local/include/boost/python/converter... I looked at the program and it seems to be searching for ~/boost/python/module.hpp, that file is there. When I point the program to these files, it doesn't pick them up: sudo ./configure --with-boost-python=/opt/local/include/boost/python LDFLAGS="-l/opt/local/include/boost/python" LDFLAGS="-L/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib" PYTHON_VERSION="2.7" I ran a few versions of this and it finds python2.7 and boost, but still can't find the boost/python part. I searched the log and I think it is not picking up the correct flags for boost/python because it outputs this: ## ----------------- ## ## Output variables. ## ## ----------------- ## ACLOCAL='${SHELL} /opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13/missing --run aclocal-1.11' AMDEPBACKSLASH='\' AMDEP_FALSE='#' AMDEP_TRUE='' AMTAR='${SHELL} /opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13/missing --run tar' AM_BACKSLASH='\' AM_DEFAULT_VERBOSITY='0' AR='ar' AUTOCONF='${SHELL} /opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13/missing --run autoconf' AUTOHEADER='${SHELL} /opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13/missing --run autoheader' AUTOMAKE='${SHELL} /opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13/missing --run automake-1.11' AWK='awk' BOOST_CPPFLAGS='-I/opt/local/include' BOOST_GRAPH_LIB='' BOOST_IOSTREAMS_LIB='' BOOST_LDFLAGS='-L/opt/local/lib' BOOST_PYTHON_LIB='' BOOST_REGEX_LIB='' I think the problem is that it's looking in /opt/local/lib for the boost libraries, but they live in /opt/local/include/boost and it isn't picking it up when I put BOOST_LDFLAGS into the ./configure command. I manually input BOOST_PYTHON_LIB and it found it but said this: checking for boostlib >= 1.38.0... yes checking whether the Boost::Python library is available... no checking whether the Boost::Iostreams library is available... no configure: error: No usable boost::iostreams found I'm not sure what else to try- I know that is where it is, am I not inputting it correctly? All the other dependencies installed through macports are also in opt/local/include. Thanks -Janna -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi, On 17/05/2011 22:22, Janna wrote:
Hi,
I went through it again and this is what I get for the boost/python location:
I think the problem is that it's looking in /opt/local/lib for the boost libraries, but they live in /opt/local/include/boost and it isn't picking it up when I put BOOST_LDFLAGS into the ./configure command. I manually input BOOST_PYTHON_LIB and it found it but said this:
not sure if there's a bit of confusion there between the headers and the libraries. Was your boost installation built with python support? Looks like you have it from macports so you can check like this: $ port installed boost The following ports are currently installed: boost @1.46.1_0+no_single+no_static+python26+universal (active) you're looking for a +python26 or +python27 I guess. The configure is looking for the libboost_python-mt.dylib which macports puts in /opt/local/lib : $ port contents boost | grep python | grep dylib /opt/local/lib/libboost_python-mt.dylib The graph-tool configure should find everything you need if you point it at the boost root directory "./configure --with-boost[=DIR]" - which in this case would be ./configure --with-boost=/opt/local there should be no need to add flags yourself after this- but if you did, they would be CPPFLAGS="-I/opt/local/include" for the header files and LDFLAGS="-L/opt/local/lib" for the libraries. If you are using macports, then why not use the portfile for graph-tool (which works very nicely and takes care of all these things)? It is recommended to use the same compiler for boost, python and graph-tool- macports provides all of them (just set aside a few hours for compilation!). regards,
checking for boostlib>= 1.38.0... yes checking whether the Boost::Python library is available... no checking whether the Boost::Iostreams library is available... no configure: error: No usable boost::iostreams found
I'm not sure what else to try- I know that is where it is, am I not inputting it correctly? All the other dependencies installed through macports are also in opt/local/include. Thanks -Janna
-- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com. _______________________________________________ graph-tool mailing list graph-tool@skewed.de http://lists.skewed.de/mailman/listinfo/graph-tool
Hi, thanks for the help- I wasn't quite sure what to look for. I did the macports installation but it fails on graph-tool - everything seems to install fine but I searched for libboost_python and it's not on my computer, so I guess the boost_python libraries were actually not installed at all. searching for boost gets me this: sudo port installed boost The following ports are currently installed: boost @1.46.1_0 (active) without the additional specifications. I will try to install boost with +python27 and see if that helps. Thanks again! -Janna -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Ok, so installing boost+python27 solved the configuration problem, but it still fails in the build. The log file says: :info:build graph_geometric.hh: In member function 'void graph_tool::get_geometric::operator()(Graph&, Pos, std::vector<std::vector<double, std::allocator<double> >, std::allocator<std::vector<double, std::allocator<double> > >
&, std::vector<std::pair<double, double>, std::allocator<std::pair<double, double> > >&, double, bool) const [with Graph = boost::UndirectedAdaptor<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, boost::no_property, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::no_property, boost::listS> >, Pos = boost::unchecked_vector_property_map<std::vector<double, std::allocator<double> >, boost::vec_adj_list_vertex_id_map<boost::no_property, long unsigned int> >]': :info:build graph_geometric.hh:163: internal compiler error: in lower_stmt, at gimple-low.c:286 :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. :info:build make[4]: *** [graph_geometric.lo] Error 1 :info:build make[4]: *** Waiting for unfinished jobs.... :info:build make[3]: *** [all-recursive] Error 1 :info:build make[2]: *** [all-recursive] Error 1 :info:build make[1]: *** [all-recursive] Error 1 :info:build make: *** [all] Error 2 :info:build shell command " cd "/opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13" && /usr/bin/make -j4 all " returned error 2 :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: the following items did not execute (for graph-tool): org.macports.activate org.macports.build org.macports.destroot org.macports.install
It seems to be hitting a bug, but I can't tell if it is in graph-tool or not. Thanks again for your help! -Janna -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi Janna, On 05/18/2011 07:51 AM, Janna wrote:
:info:build graph_geometric.hh:163: internal compiler error: in lower_stmt, at gimple-low.c:286 :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.
This is definitely not a graph-tool bug, it is a bug with the GCC from apple. I've seen this problem in some MacOS systems (I suppose it is connected to some versions of XCode). I could find only two workarounds for this: 1. Disable openmp support (install the portfile with -openmp) 2. Compile "by hand" the modules with fail to build, using FSF's GCC. For the second option, you have to be sure that the linking gets done with apple's gcc, otherwise you will get segfaults later on. BTW, it is issues like this which makes using MacOS quite annoying, in my opinion. In GNU/Linux systems, things work much more smoothly. Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>
Thanks! I will try it- I started it but the build was taking a long time and all my CPU so I'm going to run it overnight. My officemate wrote a SNP identification program that is also running into openMP problems- I feel like half my life lately is solving software installation issues, so if what you are saying about Linux is true I might seriously consider switching! -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi, I let it install over the weekend on my work computer but it still failed to build (I did it as graph-tool -openmp), I don't know what the problem is- thanks for your help! -Janna :info:build In file included from /usr/include/c++/4.2.1/ios:47, :info:build from /usr/include/c++/4.2.1/ostream:45, :info:build from /usr/include/c++/4.2.1/iostream:45, :info:build from /opt/local/include/boost/assert.hpp:82, :info:build from /opt/local/include/boost/function/function_base.hpp:20, :info:build from /opt/local/include/boost/function/detail/prologue.hpp:17, :info:build from /opt/local/include/boost/function/function_template.hpp:13, :info:build from /opt/local/include/boost/function/detail/maybe_include.hpp:13, :info:build from /opt/local/include/boost/function/function0.hpp:11, :info:build from /opt/local/include/boost/python/errors.hpp:13, :info:build from /opt/local/include/boost/python/handle.hpp:11, :info:build from /opt/local/include/boost/python/args_fwd.hpp:10, :info:build from /opt/local/include/boost/python/args.hpp:10, :info:build from /opt/local/include/boost/python.hpp:11, :info:build from numpy_bind.hh:22, :info:build from graph_bind.cc:19: :info:build /usr/include/c++/4.2.1/bits/localefwd.h:58:34: error: macro "isspace" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/localefwd.h:70:34: error: macro "isupper" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/localefwd.h:74:34: error: macro "islower" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/localefwd.h:78:34: error: macro "isalpha" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/localefwd.h:94:34: error: macro "isalnum" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/localefwd.h:102:34: error: macro "toupper" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/localefwd.h:106:34: error: macro "tolower" passed 2 arguments, but takes just 1 :info:build In file included from /usr/include/c++/4.2.1/bits/basic_ios.h:44, :info:build from /usr/include/c++/4.2.1/ios:50, :info:build from /usr/include/c++/4.2.1/ostream:45, :info:build from /usr/include/c++/4.2.1/iostream:45, :info:build from /opt/local/include/boost/assert.hpp:82, :info:build from /opt/local/include/boost/function/function_base.hpp:20, :info:build from /opt/local/include/boost/function/detail/prologue.hpp:17, :info:build from /opt/local/include/boost/function/function_template.hpp:13, :info:build from /opt/local/include/boost/function/detail/maybe_include.hpp:13, :info:build from /opt/local/include/boost/function/function0.hpp:11, :info:build from /opt/local/include/boost/python/errors.hpp:13, :info:build from /opt/local/include/boost/python/handle.hpp:11, :info:build from /opt/local/include/boost/python/args_fwd.hpp:10, :info:build from /opt/local/include/boost/python/args.hpp:10, :info:build from /opt/local/include/boost/python.hpp:11, :info:build from numpy_bind.hh:22, :info:build from graph_bind.cc:19: :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:242:53: error: macro "toupper" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:271:53: error: macro "tolower" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:814:53: error: macro "toupper" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:847:53: error: macro "tolower" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4611:44: error: macro "isspace" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4629:44: error: macro "isupper" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4635:44: error: macro "islower" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4641:44: error: macro "isalpha" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4665:44: error: macro "isalnum" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4677:44: error: macro "toupper" passed 2 arguments, but takes just 1 :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4683:44: error: macro "tolower" passed 2 arguments, but takes just 1 :info:build In file included from /usr/include/c++/4.2.1/ios:47, :info:build from /usr/include/c++/4.2.1/ostream:45, :info:build from /usr/include/c++/4.2.1/iostream:45, :info:build from /opt/local/include/boost/assert.hpp:82, :info:build from /opt/local/include/boost/function/function_base.hpp:20, :info:build from /opt/local/include/boost/function/detail/prologue.hpp:17, :info:build from /opt/local/include/boost/function/function_template.hpp:13, :info:build from /opt/local/include/boost/function/detail/maybe_include.hpp:13, :info:build from /opt/local/include/boost/function/function0.hpp:11, :info:build from /opt/local/include/boost/python/errors.hpp:13, :info:build from /opt/local/include/boost/python/handle.hpp:11, :info:build from /opt/local/include/boost/python/args_fwd.hpp:10, :info:build from /opt/local/include/boost/python/args.hpp:10, :info:build from /opt/local/include/boost/python.hpp:11, :info:build from numpy_bind.hh:22, :info:build from graph_bind.cc:19: :info:build /usr/include/c++/4.2.1/bits/localefwd.h:58: error: 'std::isspace' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:58: error: template declaration of 'bool std::isspace' :info:build /usr/include/c++/4.2.1/bits/localefwd.h:70: error: 'std::isupper' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:70: error: template declaration of 'bool std::isupper' :info:build /usr/include/c++/4.2.1/bits/localefwd.h:74: error: 'std::islower' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:74: error: template declaration of 'bool std::islower' :info:build /usr/include/c++/4.2.1/bits/localefwd.h:78: error: 'std::isalpha' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:78: error: template declaration of 'bool std::isalpha' :info:build /usr/include/c++/4.2.1/bits/localefwd.h:94: error: 'std::isalnum' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:94: error: template declaration of 'bool std::isalnum' :info:build /usr/include/c++/4.2.1/bits/localefwd.h:102: error: 'std::toupper' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:102: error: template declaration of '_CharT std::toupper' :info:build /usr/include/c++/4.2.1/bits/localefwd.h:106: error: 'std::tolower' declared as an 'inline' variable :info:build /usr/include/c++/4.2.1/bits/localefwd.h:106: error: template declaration of '_CharT std::tolower' :info:build In file included from /usr/include/c++/4.2.1/bits/basic_ios.h:44, :info:build from /usr/include/c++/4.2.1/ios:50, :info:build from /usr/include/c++/4.2.1/ostream:45, :info:build from /usr/include/c++/4.2.1/iostream:45, :info:build from /opt/local/include/boost/assert.hpp:82, :info:build from /opt/local/include/boost/function/function_base.hpp:20, :info:build from /opt/local/include/boost/function/detail/prologue.hpp:17, :info:build from /opt/local/include/boost/function/function_template.hpp:13, :info:build from /opt/local/include/boost/function/detail/maybe_include.hpp:13, :info:build from /opt/local/include/boost/function/function0.hpp:11, :info:build from /opt/local/include/boost/python/errors.hpp:13, :info:build from /opt/local/include/boost/python/handle.hpp:11, :info:build from /opt/local/include/boost/python/args_fwd.hpp:10, :info:build from /opt/local/include/boost/python/args.hpp:10, :info:build from /opt/local/include/boost/python.hpp:11, :info:build from numpy_bind.hh:22, :info:build from graph_bind.cc:19: :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:227: error: 'btowc' is not a type :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:242: error: expected ';' before 'const' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:255: error: expected `;' before 'char_type' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:256: error: 'btowc' is not a type :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:271: error: expected ';' before 'const' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:287: error: expected `;' before 'char_type' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h: In member function '_CharT std::__ctype_abstract_base<_CharT>::towupper(int (*)(_CharT)) const': :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:228: error: '__c' was not declared in this scope :info:build /usr/include/c++/4.2.1/bits/locale_facets.h: In member function '_CharT std::__ctype_abstract_base<_CharT>::towlower(int (*)(_CharT)) const': :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:257: error: '__c' was not declared in this scope :info:build /usr/include/c++/4.2.1/bits/locale_facets.h: At global scope: :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:797: error: 'btowc' is not a type :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:814: error: expected ';' before 'const' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:829: error: expected `;' before 'char_type' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:830: error: 'btowc' is not a type :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:847: error: expected ';' before 'const' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:866: error: expected `;' before 'char_type' :info:build /usr/include/c++/4.2.1/bits/locale_facets.h: In member function 'char std::ctype<char>::towupper(int (*)(char)) const': :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:798: error: '__c' was not declared in this scope :info:build /usr/include/c++/4.2.1/bits/locale_facets.h: In member function 'char std::ctype<char>::towlower(int (*)(char)) const': :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:831: error: '__c' was not declared in this scope :info:build In file included from /usr/include/c++/4.2.1/bits/basic_ios.h:44, :info:build from /usr/include/c++/4.2.1/ios:50, :info:build from /usr/include/c++/4.2.1/ostream:45, :info:build from /usr/include/c++/4.2.1/iostream:45, :info:build from /opt/local/include/boost/assert.hpp:82, :info:build from /opt/local/include/boost/function/function_base.hpp:20, :info:build from /opt/local/include/boost/function/detail/prologue.hpp:17, :info:build from /opt/local/include/boost/function/function_template.hpp:13, :info:build from /opt/local/include/boost/function/detail/maybe_include.hpp:13, :info:build from /opt/local/include/boost/function/function0.hpp:11, :info:build from /opt/local/include/boost/python/errors.hpp:13, :info:build from /opt/local/include/boost/python/handle.hpp:11, :info:build from /opt/local/include/boost/python/args_fwd.hpp:10, :info:build from /opt/local/include/boost/python/args.hpp:10, :info:build from /opt/local/include/boost/python.hpp:11, :info:build from numpy_bind.hh:22, :info:build from graph_bind.cc:19: :info:build /usr/include/c++/4.2.1/bits/locale_facets.h: At global scope: :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4611: error: function definition does not declare parameters :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4629: error: function definition does not declare parameters :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4635: error: function definition does not declare parameters :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4641: error: function definition does not declare parameters :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4665: error: function definition does not declare parameters :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4677: error: function definition does not declare parameters :info:build /usr/include/c++/4.2.1/bits/locale_facets.h:4683: error: function definition does not declare parameters :info:build In file included from /opt/local/include/boost/algorithm/string/predicate.hpp:22, :info:build from graph_util.hh:24, :info:build from graph_filtering.hh:48, :info:build from graph_python_interface.hh:27, :info:build from graph_bind.cc:22: :info:build /opt/local/include/boost/algorithm/string/compare.hpp: In member function 'bool boost::algorithm::is_iequal::operator()(const T1&, const T2&) const': :info:build /opt/local/include/boost/algorithm/string/compare.hpp:71: error: expected primary-expression before '>' token :info:build /opt/local/include/boost/algorithm/string/compare.hpp:71: error: expected primary-expression before '>' token :info:build /opt/local/include/boost/algorithm/string/compare.hpp: In member function 'bool boost::algorithm::is_iless::operator()(const T1&, const T2&) const': :info:build /opt/local/include/boost/algorithm/string/compare.hpp:124: error: expected primary-expression before '>' token :info:build /opt/local/include/boost/algorithm/string/compare.hpp:124: error: expected primary-expression before '>' token :info:build /opt/local/include/boost/algorithm/string/compare.hpp: In member function 'bool boost::algorithm::is_not_igreater::operator()(const T1&, const T2&) const': :info:build /opt/local/include/boost/algorithm/string/compare.hpp:177: error: expected primary-expression before '>' token :info:build /opt/local/include/boost/algorithm/string/compare.hpp:177: error: expected primary-expression before '>' token :info:build CXX graph_io.lo :info:build CXX graph_properties.lo :info:build make[4]: *** [graph_bind.lo] Error 1 :info:build make[4]: *** Waiting for unfinished jobs.... :info:build make[3]: *** [all-recursive] Error 1 :info:build make[2]: *** [all-recursive] Error 1 :info:build make[1]: *** [all-recursive] Error 1 :info:build make: *** [all] Error 2 :info:build shell command " cd "/opt/local/var/macports/build/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/work/graph-tool-2.2.13" && /usr/bin/make -j4 all " returned error 2 :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: the following items did not execute (for graph-tool): org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Log for graph-tool is at: /opt/local/var/macports/logs/_Users_jannafierst_DarwinPorts_local-sources_science_graph-tool/main.log -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/... Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.
Hi, Sorry for the delay. On 05/24/2011 07:14 PM, Janna wrote:
I let it install over the weekend on my work computer but it still failed to build (I did it as graph-tool -openmp), I don't know what the problem is- thanks for your help! -Janna
This is again seems to be a weird problem with MacOS + macports, but the workaround has to be done in the source code. I've now included the necessary modifications in the git version. Could you try the "devel" Portfile available in the website? Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>
participants (3)
-
Janna -
thecolourblue -
Tiago de Paula Peixoto