The cuda version is currently checked in setcompilers.py at the same time as it looks for nvcc, though maybe this is a bad place for it. Regardless, I changed it for the time being to print an error message instead of just silently failing and sticking something way back in the logs.
We *are* requiring cuda 3.2 now though, so we'll need it on breadboard--is there an easy way to do that? --- Victor L. Minden Tufts University School of Engineering Class of 2012 On Wed, Nov 3, 2010 at 1:43 PM, Barry Smith <bsmith at mcs.anl.gov> wrote: > > On Nov 3, 2010, at 12:03 PM, Satish Balay wrote: > > > Will check the machine. Perhaps cuda.py needs version check - similar > > to cusp.py? > > > > Yes, it should have one. > > Barry > > > satish > > > > On Wed, 3 Nov 2010, Matthew Knepley wrote: > > > >> Thanks, > >> > >> Matt > >> > >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101103/1f458232/attachment.html>
