On Sun, May 22, 2011 at 08:47, Wes McKinney <wesmckinn(a)gmail.com> wrote:
On Sun, May 22, 2011 at 11:33 AM, Nicolas Pinto
>> Also, is there a public issue tracker for PyCUDA and PyOpenCL? I
>> personally find keeping track of e-mail threads to be a nightmare. I
>> hate to be a pain but like everyone else I'm +1 on putting these
>> projects on GitHub.
> +1 on (re-)opening the issue tracker on github:
BTW near as I can tell there is across-the-board exception-reporting
problems with boost.python in 64-bit Python on OS X (both PyCUDA and
PyOpenCL). I am trying to reinstall 32-bit Python on here so I can see
if the same problems occur with 32-bit...
OT but: there are some other bug reports I'd like to make about
PyCUDA...issue tracker would be nice for that ;) Here's an example:
passing scalar values (e.g. ints) to a PyCUDA kernel *only* works
right now when they are subclasses of numpy.number. This is extremely
annoying in practice.
Also, PyCUDA git HEAD does not currently build in 64-bit mode on OS X
due to a linker error (surely having something to do with the fat CUDA
binaries released earlier this year-- used to be 32-bit only).
I just built pycuda HEAD a minute ago in 32/64b (system Python 2.6.1
on 10.6.7) with no issues.
USE_SHIPPED_BOOST = True
CUDA_TRACE = False
CUDA_ENABLE_GL = True
CUDA_ENABLE_CURAND = True
CUDADRV_LIB_DIR = ['/usr/local/cuda/lib']
CUDADRV_LIBNAME = ['cuda']
CXXFLAGS = 
LDFLAGS = 
(noting that I have ARCHFLAGS='-arch i386 -arch x86_64' in my env as I
PyOpenCL mailing list