[petsc-dev] configure failed after update of OSX

[Satish Balay]

Yeah - it must have been a while since I last checked on homebrew :)

Wrt hpc.sourceforge.net - it installs in /usr/local - so it does not
conflict system stuff.

Satish

On Mon, 27 Jan 2014, Aron Ahmadia wrote:

> Satish,
> 
> Yup!  Samuel John switched homebrew over to a modern gfortran in 2012:
> 
> https://github.com/Homebrew/homebrew/commit/1751362562f9b5d56708003f0dffb88e5b2418ab
> 
> So it's been at least a year :)
> 
> I don't point people at the hpc.sourceforge builds, if I recall correctly
> they install right into your /usr/bin, which seems a bit risky to me.
> 
> Cheers,
> Aron
> 
> 
> On Tue, Jan 28, 2014 at 12:27 AM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> > I've generally recommended hpc.sourceforge as its simple, easy to
> > install and has worked for me for a long time. [Uninstall requires a
> > bit of effort though..]
> >
> > Sure - if one needs a bunch of packages including fortran -
> > homebrew/macports would be the way to go.
> >
> > We've had quiet a few maint issues with macport conflicts - and Sean
> > had been trying to resolve some of them within macpors. [And helping
> > folks here on this list]
> >
> > Previously Homebrew had gfortran-4.2. But that was a buggy version and
> > broke petsc f90 related functionality - so I didn't recommend it. But
> > now I see gfortran-4.8 in homebrew - so perhaps it will work better
> > now.
> >
> > Satish
> >
> > On Mon, 27 Jan 2014, Aron Ahmadia wrote:
> >
> > > Mark,
> > >
> > > You don't have any surprises in your configure file.  I'm not surprised
> > > that your MacPorts install broke, we saw pretty terrible breakage across
> > > the Scientific Python community, although I think Homebrew weathered the
> > > update pretty well.
> > >
> > > I'd suggest following Sean's instructions so long as you're happy with
> > Mac
> > > Ports.  The most important thing is getting your compiler stack sane, and
> > > unfortunately when you're compiling Fortran on OS X, you're going to have
> > > to deal with a half-crazed stack no matter what you do.  See Geoff's
> > > excellent summary on SciComp for future Fortran compiler options:
> > > http://scicomp.stackexchange.com/a/2470/9 -- MacPorts is a reasonable
> > > choice here.
> > >
> > > HashDist's main purpose is in helping scientists specify a software
> > stack,
> > > then reproduce it elsewhere.  It looks to me like PETSc is actually
> > > satisfying most of your stack, and the only place where you need a little
> > > help from MacPorts is the Fortran compiler, so I think HashDist would be
> > > overkill for your needs here.
> > >
> > > Cheers,
> > > Aron
> > >
> > >
> > > On Mon, Jan 27, 2014 at 6:19 PM, Mark Adams <mfadams at lbl.gov> wrote:
> > >
> > > > Sean, I seem to need to reinstall macorts.  I ran this:
> > > >
> > > > *Edit:* A binary installer for Mavericks (for the 2.2.1 bugfix release)
> > > > is now available:
> > > >
> > https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg.
> > > >
> > > > And it created a MacPorts directory in Application but this just a few
> > > > apps but no 'port' command.  Any idea what is going on here?
> > > > Thanks,
> > > > Mark
> > > >
> > > >
> > > > On Mon, Jan 27, 2014 at 11:44 AM, Sean Farley <
> > > > sean.michael.farley at gmail.com> wrote:
> > > >
> > > >>
> > > >> bsmith at mcs.anl.gov writes:
> > > >>
> > > >> >   I think resolved it by getting rid of some stuff that macports
> > put in
> > > >> maybe
> > > >>
> > > >> I just *completely* revamped the mpi ports in macports and would like
> > to
> > > >> know if these types of problems still exist.
> > > >>
> > > >> >   MPICH or libtool assumes certain files are there if other files
> > are
> > > >> there (without checking for them)
> > > >> >
> > > >> >    Barry
> > > >> >
> > > >> > On Jan 27, 2014, at 10:36 AM, Satish Balay <balay at mcs.anl.gov>
> > wrote:
> > > >> >
> > > >> >> On Mon, 27 Jan 2014, Jed Brown wrote:
> > > >> >>
> > > >> >>> Mark Adams <mfadams at lbl.gov> writes:
> > > >> >>>
> > > >> >>>> It seems to want /opt/local/lib/liblzma.la
> > > >> >>>> I do have /opt/local/lib/liblzma.a
> > > >> >>>
> > > >> >>> There is no explicit reference to liblzma in either PETSc or
> > MPICH.
> > > >>  Can
> > > >> >>> you send PETSC_ARCH/externalpackages/mpich*/config.log?
> > > >> >>
> > > >> >> Ah - perhaps its a buggy libtool. Presumably its picked up from
> > > >> >> /opt/local/bin/libtool - aka macports - and you have a broken
> > macports
> > > >> >> install.
> > > >> >>
> > > >> >> Satish
> > > >> >>
> > > >> >>
> > > >>
> > > >>
> > > >
> > >
> >
> >
>