Glad it eventually worked for you. Sorry I forgot to mention the readline bug. My brain is not big enough to remember all those steps. It does cause a doctest failure.
As you probably have realized, Michael already has a patch for it in the pipeline, it will be fixed in 3.1.2 I believe. If you want sage to have a working command line, you could use the newer python spkg. D M: +61 423 535 397 W: +61 2 6125 8260 On 12/09/2008, at 19:52, Simon Beaumont <[EMAIL PROTECTED]> wrote: > > I am happy to report that boost_1_35_0, pycuda 0.9 (plus my hacks) are > all now working and tested against this build. Thanks to David for his > help and patches. Game on. > > On Sep 12, 1:28 am, Simon Beaumont <[EMAIL PROTECTED]> wrote: >> Ok - got there in the end... >> >> I did a fresh build (OS X 10.5.4 intel) with 3.1.1 sources. >> Applied David's patches and fixed up the externs in cvxopt sources as >> he indicated. All built just fine. >> >> All test pass apart from trace - which is no doubt due to sage >> command >> line not being able to load readline - which is odd since it has been >> built ok - I guess it's the python framework that is not loading >> this. >> I'm sure there's an easy fix. >> >> Now onto patching boost and seeing if this wont all play nicely >> together. >> >> Be nice is this was the default (supported) build for OS X since >> nothing else is a starter if packages need to link against the >> python. >> I only want to run one python and I want all my python code and any >> packages I use to play in sage. That's the whole point for me - >> extensibility in all directions. > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
