On Tue, 28 Jan 2014, Sean Farley wrote: > > [email protected] writes: > > > Oh yes. I had a use-make=make commended out. I uncommented it and its > > seems to have gotten MPICH installed. > > There is a newly (only a few days old) updated mpich port that I now use > with my petsc install.
This is not really a fix - as the 'gmake' error will pop up with petsc part of the build aswell. > > > On Tue, Jan 28, 2014 at 1:26 PM, Satish Balay <[email protected]> wrote: > > > >> I'll have to check back my e-mail archive - but I think > >> '/opt/local/bin/gmake' is broken. Don't you have /usr/bin/make? > >> > >> I thought petsc configure prefred /usr/bin/make - if it was found. > >> > >> One more -ve for macports.. > > There is a fundamental problem with using two stacks. Similar, I think, > to trying to simultaneously link to libc++ and libstdc++. It is just > asking for trouble. I'm not sure how this is causing gmake 'internal' error.. Satish
