[petsc-dev] configure failed after update of OSX

[Satish Balay]

On Tue, 28 Jan 2014, Sean Farley wrote:

> The gmake issue could be a lot of things:
> 
> - something weird with mpich's autoconf
> - libtool problems
> - gmake itself
> - path issues

The issue is with 'gmake - j 7 all' with mpich build [and similarly
petsc build] after configure [of the corresponding package] is
completed.

> 
> I'll try to reproduce this again to see if it happens on my machine.
> 
> Maybe I should just advise not to use --download-*mpi*. Wrapping
> compilers is tricky. For example, Mark seems to have upgraded to
> Mavericks, yet in his script he is specifying gcc/g++ which is no longer
> distributed with Xcode.

Apple [Xcode5] provides a binary called /usr/bin/gcc - which is
'clang'.  [Yeah naming 'clang' as 'gcc' is funky - but I think apple
does that to not break user makefiles that have 'gcc' hardcoded]

Satish

> 
> For my own work, I install the Apple clang + gfortran 4.8 most of the
> time, via
> 
> $ sudo port install mpich-default
> $ sudo port select --set mpi mpich-mp-fortran
> 
> Then try to build PETSc (minus the --download-mpich and CC, CXX, FC
> options). You could also try to install most of the external packages:
> 
> $ sudo port install hypre ml parmetis metis hdf5-18 netcdf triangle \
> superlu superlu_dist mumps
> 
> ctetgen and exodusii aren't in MacPorts but (assuming the licenses allow
> it) I could add them.
>