[petsc-dev] configure failing because of old nvcc

[Barry Smith]

  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