[petsc-dev] configure failed after update of OSX

[Aron Ahmadia]

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
>> >>
>> >>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140127/8d231bd5/attachment.html>