[petsc-dev] configure failing because of old nvcc

Matthew Knepley knepley at gmail.com
Fri Nov 5 13:34:39 CDT 2010


I did this already, have you pulled?

   Matt

On Fri, Nov 5, 2010 at 1:29 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:

>
> On Nov 5, 2010, at 1:18 PM, Satish Balay wrote:
>
> > I think part of the issue is the configure model for compiler detection.
> >
> > Perhaps we want buildsystem to detect/set compilers as it sees.  And
> > then petsc side of configure to check if this functionality exists -
> > and then use it? [with --with-cuda=1 flag in cuda.py?]
> >
> > There was a recent change to do version check of nvcc in buildsystem -
> > instead of the prior check in cuda.py. [I just striped out the one
> > from cuda.py - because it was broken].
> >
> > If so - perhaps the fix is to remove this check from Buildsystem
> > [setCompilers.py - where it only determines cuda attributes like
> > version - as stashes this info] - and place the version check back in
> > cuda.py?
>
>   Yes, that is right.
>
>   Barry
>
> >
> > Satish
> >
> >
> > On Fri, 5 Nov 2010, Barry Smith wrote:
> >
> >>
> >>  You are correct, it should only stop on this if the user asked for
> --with-cuda  Victor can you fix this.
> >>
> >>
> >> On Nov 5, 2010, at 12:57 PM, Lisandro Dalcin wrote:
> >>
> >>> Do we really want this? Perhaps CUDA should be just disabled, instead
> >>> of configure failing? Note that I've not actually asked for a
> >>> CUDA-enabled build:
> >>>
> >>>
> >>> $ cat linux-gnu/conf/reconfigure-linux-gnu.py
> >>> #!/usr/bin/python
> >>> if __name__ == '__main__':
> >>> import sys
> >>> import os
> >>> sys.path.insert(0, os.path.abspath('config'))
> >>> import configure
> >>> configure_options = [
> >>>   'PETSC_ARCH=linux-gnu',
> >>>   '--with-shared-libraries=1',
> >>> ]
> >>> configure.petsc_configure(configure_options)
> >>>
> >>>
> >>> [dalcinl at nikola dev]$ python linux-gnu/conf/reconfigure-linux-gnu.py
> >>>
> ===============================================================================
> >>>            Configuring PETSc to compile on your system
> >>>
> ===============================================================================
> >>> TESTING: checkCUDACompiler from
> >>>
> config.setCompilers(config/BuildSystem/config/se===============================================================================
> >>> ** CUDA Error: PETSc requires nvcc version 3.2 when compiling with
> --withcuda **
> >>>
> ===============================================================================
> >>>
> *******************************************************************************
> >>>       CONFIGURATION CRASH  (Please send configure.log to
> >>> petsc-maint at mcs.anl.gov)
> >>>
> *******************************************************************************
> >>>
> >>>
> >>>
> >>> --
> >>> Lisandro Dalcin
> >>> ---------------
> >>> CIMEC (INTEC/CONICET-UNL)
> >>> Predio CONICET-Santa Fe
> >>> Colectora RN 168 Km 472, Paraje El Pozo
> >>> Tel: +54-342-4511594 (ext 1011)
> >>> Tel/Fax: +54-342-4511169
> >>
> >>
> >
>
>


-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101105/d723d6c3/attachment.html>


More information about the petsc-dev mailing list