<div dir="ltr">Mark,<div><br></div><div>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.</div>
<div><br></div><div>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: <a href="http://scicomp.stackexchange.com/a/2470/9">http://scicomp.stackexchange.com/a/2470/9</a> -- MacPorts is a reasonable choice here.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Cheers,</div><div>Aron</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 27, 2014 at 6:19 PM, Mark Adams <span dir="ltr"><<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sean, I seem to need to reinstall macorts. I ran this:<div><br></div><div><strong style="margin:0px;padding:0px;border:0px;font-size:14px;vertical-align:baseline;color:rgb(51,51,51);font-family:'Lucida Grande','Lucida Sans Unicode','Lucida Sans',Tahoma,sans-serif;line-height:19.600000381469727px">Edit:</strong><span style="color:rgb(51,51,51);font-family:'Lucida Grande','Lucida Sans Unicode','Lucida Sans',Tahoma,sans-serif;font-size:14px;line-height:19.600000381469727px"> A binary installer for Mavericks (for the 2.2.1 bugfix release) is now available:</span><a href="https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg" style="margin:0px;padding:0px;border:0px;font-size:14px;vertical-align:baseline;text-decoration:none;color:rgb(113,168,213);font-family:'Lucida Grande','Lucida Sans Unicode','Lucida Sans',Tahoma,sans-serif;line-height:19.600000381469727px" target="_blank">https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg</a><span style="color:rgb(51,51,51);font-family:'Lucida Grande','Lucida Sans Unicode','Lucida Sans',Tahoma,sans-serif;font-size:14px;line-height:19.600000381469727px">.</span><br>
</div><div><span style="color:rgb(51,51,51);font-family:'Lucida Grande','Lucida Sans Unicode','Lucida Sans',Tahoma,sans-serif;font-size:14px;line-height:19.600000381469727px"><br></span></div><div>
<font color="#333333" face="Lucida Grande, Lucida Sans Unicode, Lucida Sans, Tahoma, sans-serif"><span style="font-size:14.666666984558105px;line-height:19.600000381469727px">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?</span></font></div>
<div><font color="#333333" face="Lucida Grande, Lucida Sans Unicode, Lucida Sans, Tahoma, sans-serif"><span style="font-size:14.666666984558105px;line-height:19.600000381469727px">Thanks,</span></font></div><div><font color="#333333" face="Lucida Grande, Lucida Sans Unicode, Lucida Sans, Tahoma, sans-serif"><span style="font-size:14.666666984558105px;line-height:19.600000381469727px">Mark</span></font></div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 27, 2014 at 11:44 AM, Sean Farley <span dir="ltr"><<a href="mailto:sean.michael.farley@gmail.com" target="_blank">sean.michael.farley@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br>
<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a> writes:<br>
<br>
> I think resolved it by getting rid of some stuff that macports put in maybe<br>
<br>
</div>I just *completely* revamped the mpi ports in macports and would like to<br>
know if these types of problems still exist.<br>
<div><div><br>
> MPICH or libtool assumes certain files are there if other files are there (without checking for them)<br>
><br>
> Barry<br>
><br>
> On Jan 27, 2014, at 10:36 AM, Satish Balay <<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>> wrote:<br>
><br>
>> On Mon, 27 Jan 2014, Jed Brown wrote:<br>
>><br>
>>> Mark Adams <<a href="mailto:mfadams@lbl.gov" target="_blank">mfadams@lbl.gov</a>> writes:<br>
>>><br>
>>>> It seems to want /opt/local/lib/<a href="http://liblzma.la" target="_blank">liblzma.la</a><br>
>>>> I do have /opt/local/lib/liblzma.a<br>
>>><br>
>>> There is no explicit reference to liblzma in either PETSc or MPICH. Can<br>
>>> you send PETSC_ARCH/externalpackages/mpich*/config.log?<br>
>><br>
>> Ah - perhaps its a buggy libtool. Presumably its picked up from<br>
>> /opt/local/bin/libtool - aka macports - and you have a broken macports<br>
>> install.<br>
>><br>
>> Satish<br>
>><br>
>><br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>