On 01/07/2014 04:48 PM, Gerry Steele wrote:
Thanks Tiago
I assumed for some reason that those paths would be taken care of by --with-boost
However after building numpy and then attempting to build scipy and finding it needs BLAS which is written in fortran I have stopped trying to get graph-tool to work. There are far too many dependencies for it to be a reasonable product for my use case. I'll revert to boost-graph directly in c++ for my needs.
That's fine. Package dependencies is a problem which best solved by computers, not humans. Scipy is a standard framework for doing scientific analysis with python. It is available in any distribution I known of. Essentially the problem here is that you are trying to do by hand what your operating system does for free, and what your system administrator is paid to do (I hope). Unfortunately, this seems like a rather common scenario... Nevertheless, the real problem is that you are stuck with an ancient operating system, with no sysadmin rights. It is not a problem with the "product", as I see it. The single most frequent complain I hear about graph-tool is that it is difficult to install because of the dependencies. The dependencies are all standard software, available in all systems with some form of package management. I even provide pre-compiled packages for some of these systems. What else should I do? From my perspective, it doesn't make any sense do drop an essential and very useful thing like interoperability with scipy/numpy because people can't install it by hand... Best, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>