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
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.
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 rea
Thanks for that... someone might care to fix it... I think it used to
work. It calls sage -python passing all the command line.
More importantly what would be involved in using the system framework
based python - would it just be a case of setting $PYTHON to be /usr/
bin/python?
Cheers,
Simon
On Aug 28, 4:34 pm, Simon Beaumont <[EMAIL PROTECTED]> wrote:
> Well any python code fails to work as expected:
>
> try: sage-python -c "import sys"
> File "", line 1
> import
> ^
> SyntaxError: invalid syntax
>
> ... -c "print;print" # will print two line feeds however
>
> this came
I have pycuda working on OSX 10.5.2 with the standard framework based
python and nv CUDA 2.0... now for the hacks!
Not at all sure about the right direction for this CUDA stuff yet.
Simon
On Aug 29, 12:29 am, Simon Beaumont <[EMAIL PROTECTED]> wrote:
> On Aug 28, 11:22 pm, David Philp <[EMAIL P
On 29/08/2008, at 9:29 AM, Simon Beaumont wrote:
> On Aug 28, 11:22 pm, David Philp <[EMAIL PROTECTED]> wrote:
>> On 29/08/2008, at 7:56 AM, mabshoff wrote:
>>
>>> David Philip has been playing with building PyCuDA against Sage's
>>> Python on OSX.
>>
>> No!!! I'd love to do it but I haven't go
Well any python code fails to work as expected:
try: sage-python -c "import sys"
File "", line 1
import
^
SyntaxError: invalid syntax
... -c "print;print" # will print two line feeds however
this came up when trying to configure boost for sage, wherein
configure has:
$PYTHON -c "
On Aug 28, 11:22 pm, David Philp <[EMAIL PROTECTED]> wrote:
> On 29/08/2008, at 7:56 AM, mabshoff wrote:
>
> > David Philip has been playing with building PyCuDA against Sage's
> > Python on OSX.
>
> No!!! I'd love to do it but I haven't got time for CUDA. I've been
> using boost.python, for
On 29/08/2008, at 7:56 AM, mabshoff wrote:
> David Philip has been playing with building PyCuDA against Sage's
> Python on OSX.
No!!! I'd love to do it but I haven't got time for CUDA. I've been
using boost.python, for the sake of /other/ C++ code of mine. I
originally tried to sort of bo
On Aug 28, 2:32 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 28, 2008 at 1:19 PM, Simon Beaumont <[EMAIL PROTECTED]> wrote:
Hi,
> > got a rather weird one - os x 10.5.2 sage 3.1.1 (binary build) I am
> > trying to build boost (python) for this version on os x - so I can get
> >
On Thu, Aug 28, 2008 at 1:19 PM, Simon Beaumont <[EMAIL PROTECTED]> wrote:
>
> got a rather weird one - os x 10.5.2 sage 3.1.1 (binary build) I am
> trying to build boost (python) for this version on os x - so I can get
> pycuda going against the OS X 2.0 cuda.
>
> well the python (python-sage) se
12 matches
Mail list logo
