[petsc-dev] configure failed after update of OSX

[Barry Smith]

On Jan 28, 2014, at 1:10 PM, Mark Adams <mfadams at lbl.gov> wrote:

> I managed to get macports to rebuild.  It was not that hard as it turns out, I was just confused about exactly what to do.  GDB broke but I was able to install it after macports updated outdated packages.  PETSc still seem to fail in MPICH, however.

   Correction, MPICH failed to install (probably for the same reason as before)

  Barry

> 
> 
> 
> On Tue, Jan 28, 2014 at 12:54 PM, Matthew Knepley <knepley at gmail.com> wrote:
> On Tue, Jan 28, 2014 at 12:51 PM, Jed Brown <jed at jedbrown.org> wrote:
> Satish Balay <balay at mcs.anl.gov> writes:
> > I agree a better package management system [aka macports/homebrew]
> > should be preferable. But with all the wierd issues that keep comping
> > up with users using macports on petsc lists - I can't convince myself
> > that it is a better recommendation.
> 
> People either need a reliable way to upgrade or the stack will get out
> of date.  Also, system upgrades will be stop-the-world events with
> unknown system changes and the only safe thing is to reinstall the
> entire stack.  Very few people can remember all the installation quirks
> they have gone through, and even then, it takes time to reinstall
> everything.
> 
> This is largely ideology. Some of us have used OSX for development for years
> with little productivity impact.
> 
>   Matt
>  
> > I would aswell recommend virtualbox with linux as a superior choice.
> 
> I recommend
> 
>   # dd if=/dev/zero of=/dev/disk0
> 
> and install a decent operating system with a package manager on your
> now-impeccably-clean disk.
> 
> 
> 
> -- 
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener
> 
> <configure.log>