Hi Dave, thanks for the first piece of feedback. I'll wait for the logs in order to get an idea whether BuildSystem, FindCUDA.cmake, or any other component is causing the troubles.
Best regards, Karli On 03/20/2013 10:17 AM, Nystrom, William D wrote: > Hi Karli, > > I ran a test build last night and it failed. It was a relatively simple > configuration where > I was downloading mpich and cmake and building with threads, cuda and the > txpetscgpu > package. I was building on a Fedora 17 machine with Cuda 5. The failure > seem to be > associated with cmake. When I get home this evening, I could send you the > configure > and make logs. I did not have time this morning before leaving for work. I > wanted to > give you some early feedback even though the logs will have to wait till this > evening. > > Thanks, > > Dave > > -- > Dave Nystrom > LANL HPC-5 > Phone: 505-667-7913 > Email: wdn at lanl.gov > Smail: Mail Stop B272 > Group HPC-5 > Los Alamos National Laboratory > Los Alamos, NM 87545 > > > ________________________________________ > From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on > behalf of Karl Rupp [rupp at mcs.anl.gov] > Sent: Tuesday, March 19, 2013 4:04 PM > To: petsc-dev at mcs.anl.gov > Subject: Re: [petsc-dev] CMake-assisted CUDA builds ready > > Hi Dave, > > perfect, thanks! > I should add that a reconfigure is needed. It won't work with re-running > make only. > > Best regards, > Karli > > > On 03/19/2013 04:59 PM, Nystrom, William D wrote: >> Hi Karli, >> >> I will try this soon and report back when I have results. >> >> Thanks, >> >> Dave >> >> ________________________________________ >> From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on >> behalf of Karl Rupp [rupp at mcs.anl.gov] >> Sent: Tuesday, March 19, 2013 3:58 PM >> To: For users of the development version of PETSc >> Subject: [petsc-dev] CMake-assisted CUDA builds ready >> >> Dear all, >> >> I just merged the CMake-based builds for CUDA-packages into 'next', >> reducing compilation times considerably compared to the old legacy >> builds. While the legacy builds print something like >> 'libfast in <DIR>' >> the new CMake-based builds print the usual percentage counters in front. >> >> Any feedback on the proper functionality (both positive and negative) >> are appreciated. >> >> Thanks and best regards, >> Karli >> >
