Should cmake.py be changed to have
self.requirescxx11 = 1
Then at least you get an error message instead of having to wade into the
configure output?
Barry
> On Jun 21, 2018, at 9:41 PM, Balay, Satish <[email protected]> wrote:
>
> Hm - we've generally used preinstalled cmake on LCFs - so its not
> clear to me when cmake switched to requring C++11. [this issue never
> came up with so far]
>
> So - suggest avoiding --download-cmake - and use 'module load cmake'
> or whatever is appropriate on titan.
>
> Satish
>
> On Thu, 21 Jun 2018, Smith, Barry F. wrote:
>
>> We now require C++11 to build basic packages like metis? Come on, is that
>> really necessary? Do we really need this recent a version of cmake?
>>
>>
>>
>>
>> Error running configure on CMAKE: Could not execute "cd
>> /autofs/nccs-svm1_home1/adams/petsc/arch-titan-opt64-pgi/externalpackages/cmake-3.11.1
>> && ./configure
>> --prefix=/autofs/nccs-svm1_home1/adams/petsc/arch-titan-opt64-pgi
>> --parallel=24":
>> ---------------------------------------------
>> CMake 3.11.1, Copyright 2000-2018 Kitware, Inc. and Contributors
>> Found GNU toolchain
>> C compiler on this system is: gcc
>> ---------------------------------------------
>> Error when bootstrapping CMake:
>> Cannot find a C++ compiler supporting C++11 on this system.
>> Please specify one using environment variable CXX.
>> See cmake_bootstrap.log for compilers attempted.
>>
>>
>>> On Jun 21, 2018, at 5:54 PM, Mark Adams <[email protected]> wrote:
>>>
>>> I am getting a cmake error on Titan...
>>> <configure.log>
>>
>
