Hi, Those changes look good, and fix the configure problems. It seems to be compiling away just fine (I'll let you know in a day or so if it finishes :) ) It is unfortunate about the boost random libraries- they seemed to me very well designed, and they should be more carefully maintainted. I am not so sure the tr1 random libraries are better maintained. Anyway, it would only be an issue if we wanted to make a macport using the gcc-4.2 compiler (which chokes on tr1::random). On Mon, Jan 25, 2010 at 1:17 PM, Tiago de Paula Peixoto <tiago@forked.de> wrote:
Hi
On 01/25/2010 11:05 AM, tcb wrote:
Ok, you could use sed to edit the file in place, instead of reading it as a string- something like:
eval sed -i -e "s/-nostdlib/-nostdlib -lstdc++/g" libtool
Indeed, this will probably solve the problem.
I committed all the necessary modifications to the git repository. Could you please get the new git version, and see if it works for you?
Be careful, there are some serious bugs with the boost random library! Take a look at: http://lists.boost.org/boost-users/2009/05/48444.php
I switched to tr1, since the boost::random stuff seems a bit abandoned. However the tr1 has not entirely stabilized yet, and you need gcc 4.4 or newer to use it.
Oops, I hadn't seen that- I saw no indication that there were any such problems with the boost random library (although this follow up mail seems to suggest the problems were fixed as of 2009-05-30 http://lists.boost.org/boost-users/2009/05/48582.php). Unfortunately there is very little information on what works in the tr1 libraries across different compiler versions.
The tr1 should eventually stabilize, and things should change less and less in the next versions... Boost::random on the other hand does not seem to have he necessary maintenance a RNG library needs to have. Even though the problem in question was fixed, it took quite some time for it to be detected, and according to other people, it is still has some other serious problems left.
I hear GCC 4.5 will have improved template performance, since they switched to O(1) instantiation, instead of O(N).
Ok, that's good to hear. If I recompile with gcc-4.5 then I also need to recompile my whole python stack with 4.5 too (including numpy and scipy etc...)- so that is my motivation to get something working with gcc-4.2.
No, it is not so drastic. There was a C++ ABI change after 4.2 (IIRC), but the interface to C libraries (such as python, numpy, etc) should be stable. You should only have to recompile the boost libraries. And if you do it now with gcc 4.4, it should still be compatible with 4.5.
Cheers, Tiago
_______________________________________________ graph-tool mailing list graph-tool@forked.de http://lists.forked.de/mailman/listinfo/graph-tool