I recall the pci bus ID behavior changing between... 4.0 and 4.1 maybe? It swapped from being a property-like thing to being a callable, with only changing the underlying cuda version (no PyCUDA update).
What version of cuda are you using? Eli On Tue, May 1, 2012 at 11:50 AM, Serge Rey <[email protected]> wrote: > Hi, > > Following the install instructions for PyCuda on Lion I'm able to > build and install > without any errors. However if I run the test I'm getting: > > Traceback (most recent call last): > File "test_driver.py", line 4, in <module> > from pycuda.tools import mark_cuda_test > File > "/Library/Python/2.7/site-packages/pycuda-2011.2.2-py2.7-macosx-10.7-intel.egg/pycuda/tools.py", > line 30, in <module> > import pycuda.driver as cuda > File > "/Library/Python/2.7/site-packages/pycuda-2011.2.2-py2.7-macosx-10.7-intel.egg/pycuda/driver.py", > line 2, in <module> > from pycuda._driver import * > ImportError: > dlopen(/Library/Python/2.7/site-packages/pycuda-2011.2.2-py2.7-macosx-10.7-intel.egg/pycuda/_driver.so, > 2): Symbol not found: _cuDeviceGetByPCIBusId > Referenced from: > /Library/Python/2.7/site-packages/pycuda-2011.2.2-py2.7-macosx-10.7-intel.egg/pycuda/_driver.so > Expected in: flat namespace > in > /Library/Python/2.7/site-packages/pycuda-2011.2.2-py2.7-macosx-10.7-intel.egg/pycuda/_driver.so > > > I've got the CUDA tookit and drivers installed and paths dialed in > accordingly, so I'm wondering if anyone has an idea of what might be going > wrong? > > Thanks, > > > -- > Sergio (Serge) Rey > Professor, School of Geographical Sciences and Urban Planning > GeoDa Center for Geospatial Analysis and Computation > Arizona State University > http://geoplan.asu.edu/rey > > Editor, International Regional Science Review > http://irx.sagepub.com > > _______________________________________________ > PyCUDA mailing list > [email protected] > http://lists.tiker.net/listinfo/pycuda _______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
