[petsc-users] PETSc 3.5.2 on Mac OS X Yosemite, configuring gives C preprocessor error

Patrick Sanan patrick.sanan at gmail.com
Mon Jan 19 01:52:17 CST 2015


On 18/01/15 09:48 PM, Barry Smith wrote:
>    We need configure.log
>
>     You do not need --download-blaslapack Apple always has them
As of OS X 10.9 the BLAS Apple provided was known to have bugs. I only 
noticed any issue (If I remember correctly, "make test" failed) when 
configuring in single precision. However, this might be a reason to have 
petsc download BLAS/Lapack despite the libraries being available in 
Apple's framework.
>
>     Suggest just running without passing the compiler names also.
>
>    Barry
>
>> On Jan 18, 2015, at 2:45 PM, Justin Dong <jdong217 at gmail.com> wrote:
>>
>> Hi all,
>>
>> I just updated to OS X Yosemite. I have the latest XCode and also reinstalled command line developer tools.
>>
>> When I try to install PETSc, I get the following error:
>>
>> ./configure --with-cc=gcc --with-cxx=g++ --with-fc=gfortran --download-fblaslapack --download-mpich --with-debugging=0
>>
>> ===============================================================================
>>
>>               Configuring PETSc to compile on your system
>>
>> ===============================================================================
>>
>> TESTING: checkCPreprocessor from config.setCompilers(config/BuildSystem/config/setCompilers.py:568)                        *******************************************************************************
>>
>>           UNABLE to CONFIGURE with GIVEN OPTIONS    (see configure.log for details):
>>
>> -------------------------------------------------------------------------------
>>
>> Cannot find a C preprocessor
>>
>> *******************************************************************************
>>
>>
>>
>> Can someone explain to me what's going on here?
>>
>>
>>
>> Thanks,
>>
>> Justin
>>



More information about the petsc-users mailing list