On Mon, 6 Jun 2011 17:15:43 -0700, Bryan Catanzaro <catan...@eecs.berkeley.edu> wrote: > Hi - > In setting up a new PyCUDA installation recently from Git I came across two > issues, and made a patch that fixed them on my system. > > Problem #1: The CURAND module requires linking to libcurand.so, which is > found in the directory with the CUDA Runtime, which on my system is in a > different default place (/usr/local/cuda/lib64) than the directory with the > CUDA driver (/usr/lib). To change this, I added some additional options to > specify: > - The name of the CUDA Runtime library (with default). > - The directory where the CUDA Runtime is found > I also amended the description of how to compile _curand with the location > CUDA Runtime Directory. Besides allowing the _curand.so module that comes > with PyCUDA to be properly built, this change also benefits projects using > Codepy to generate CUDA runtime code, as the Copperhead project does, since > CUDA Runtime information is located in the aksetup-defaults file along with > the other CUDA configuration information.
Merged, thx. > Problem #2: The USE_SHIPPED_BOOST option defaults to True. If you're using > configure.py to set up your siteconf.py, this is a problem. If you omit > --use-shipped-boost, the default of True means that you will use the shipped > boost anyway. So, there's no way to use a system Boost without manually > editing siteconf.py after running configure. The easy fix for this is just > to change the default to false. Nah, I like that default. But I've made the (slightly nonsensical-sounding) flag --no-use-shipped-boost. Hope this helps. Thanks for your patch, Andreas
pgpS8PtBk6cfv.pgp
Description: PGP signature
_______________________________________________ PyCUDA mailing list PyCUDA@tiker.net http://lists.tiker.net/listinfo/pycuda
