<div dir="ltr">To echo what Aron said, I wouldn't point people at the <a href="http://hpc.sourceforge.net">hpc.sourceforge.net</a> builds. They do install directly into /usr/bin, and it's a pain in the ass to undo. The R/AT&T build of gcc was better, but also installed into /usr/bin, and was also a pain in the ass to uninstall.<div>
<br></div><div>Having used both MacPorts (2010-2012) and Homebrew (2012-present), I find Homebrew to be a better experience, especially if you only need a small number of packages for development. MacPorts used to insist on its own stack, which meant that if you wanted gfortran, you also had to install many other packages.</div>
<div><br></div><div>I generally developed using gcc 4.2 because I found cross-version linking to be a pain in the ass. I've also installed gcc 4.8 via the homebrew/versions tap and that's worked well, too.</div><div>
<br></div><div>Python is sort of broken in both MacPorts and Homebrew. If you look at the GitHub issues, there's been a lot of traffic related to Python in Homebrew lately because they completely revamped how they handle Python in their build recipes, which then broke some Python packages installed via Homebrew. Last I checked, Python was more broken in MacPorts and required lots of hacks to get things to work, but it's been a while since I've used MacPorts. I think the best policy is to rely on the package manager for as little Python software as possible, and install the rest of your Python stack in an isolated manner; I use pyenv, pip, & virtualenv. Conda sort of does something similar, but I feel like conda is a great build system with too many other responsibilities.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jan 27, 2014 at 9:53 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">BTW: gfortran from 'R' would install in /usr. It had an uninstaller<br>
[so was initially attractive to us].<br>
<br>
However if I remember correctly - it overwrote one of the libgcc_xx.a<br>
stuff that came with Xcode - and uninstalling it resulted in a broken<br>
gcc [I had to delete/reinstall xcode after that]<br>
<br>
There were other issues aswell. Perhaps Sean remembers them better..<br>
This was many osx/xcode versions ago.<br>
<span class="HOEnZb"><font color="#888888"><br>
Satish<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Mon, 27 Jan 2014, Satish Balay wrote:<br>
<br>
> Yeah - it must have been a while since I last checked on homebrew :)<br>
><br>
> Wrt <a href="http://hpc.sourceforge.net" target="_blank">hpc.sourceforge.net</a> - it installs in /usr/local - so it does not<br>
> conflict system stuff.<br>
><br>
> Satish<br>
><br>
> On Mon, 27 Jan 2014, Aron Ahmadia wrote:<br>
><br>
> > Satish,<br>
> ><br>
> > Yup! Samuel John switched homebrew over to a modern gfortran in 2012:<br>
> ><br>
> > <a href="https://github.com/Homebrew/homebrew/commit/1751362562f9b5d56708003f0dffb88e5b2418ab" target="_blank">https://github.com/Homebrew/homebrew/commit/1751362562f9b5d56708003f0dffb88e5b2418ab</a><br>
> ><br>
> > So it's been at least a year :)<br>
> ><br>
> > I don't point people at the hpc.sourceforge builds, if I recall correctly<br>
> > they install right into your /usr/bin, which seems a bit risky to me.<br>
> ><br>
> > Cheers,<br>
> > Aron<br>
> ><br>
> ><br>
> > On Tue, Jan 28, 2014 at 12:27 AM, Satish Balay <<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>> wrote:<br>
> ><br>
> > > I've generally recommended hpc.sourceforge as its simple, easy to<br>
> > > install and has worked for me for a long time. [Uninstall requires a<br>
> > > bit of effort though..]<br>
> > ><br>
> > > Sure - if one needs a bunch of packages including fortran -<br>
> > > homebrew/macports would be the way to go.<br>
> > ><br>
> > > We've had quiet a few maint issues with macport conflicts - and Sean<br>
> > > had been trying to resolve some of them within macpors. [And helping<br>
> > > folks here on this list]<br>
> > ><br>
> > > Previously Homebrew had gfortran-4.2. But that was a buggy version and<br>
> > > broke petsc f90 related functionality - so I didn't recommend it. But<br>
> > > now I see gfortran-4.8 in homebrew - so perhaps it will work better<br>
> > > now.<br>
> > ><br>
> > > Satish<br>
> > ><br>
> > > On Mon, 27 Jan 2014, Aron Ahmadia wrote:<br>
> > ><br>
> > > > Mark,<br>
> > > ><br>
> > > > You don't have any surprises in your configure file. I'm not surprised<br>
> > > > that your MacPorts install broke, we saw pretty terrible breakage across<br>
> > > > the Scientific Python community, although I think Homebrew weathered the<br>
> > > > update pretty well.<br>
> > > ><br>
> > > > I'd suggest following Sean's instructions so long as you're happy with<br>
> > > Mac<br>
> > > > Ports. The most important thing is getting your compiler stack sane, and<br>
> > > > unfortunately when you're compiling Fortran on OS X, you're going to have<br>
> > > > to deal with a half-crazed stack no matter what you do. See Geoff's<br>
> > > > excellent summary on SciComp for future Fortran compiler options:<br>
> > > > <a href="http://scicomp.stackexchange.com/a/2470/9" target="_blank">http://scicomp.stackexchange.com/a/2470/9</a> -- MacPorts is a reasonable<br>
> > > > choice here.<br>
> > > ><br>
> > > > HashDist's main purpose is in helping scientists specify a software<br>
> > > stack,<br>
> > > > then reproduce it elsewhere. It looks to me like PETSc is actually<br>
> > > > satisfying most of your stack, and the only place where you need a little<br>
> > > > help from MacPorts is the Fortran compiler, so I think HashDist would be<br>
> > > > overkill for your needs here.<br>
> > > ><br>
> > > > Cheers,<br>
> > > > Aron<br>
> > > ><br>
> > > ><br>
> > > > On Mon, Jan 27, 2014 at 6:19 PM, Mark Adams <<a href="mailto:mfadams@lbl.gov">mfadams@lbl.gov</a>> wrote:<br>
> > > ><br>
> > > > > Sean, I seem to need to reinstall macorts. I ran this:<br>
> > > > ><br>
> > > > > *Edit:* A binary installer for Mavericks (for the 2.2.1 bugfix release)<br>
> > > > > is now available:<br>
> > > > ><br>
> > > <a href="https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg" target="_blank">https://distfiles.macports.org/MacPorts/MacPorts-2.2.1-10.9-Mavericks.pkg</a>.<br>
> > > > ><br>
> > > > > And it created a MacPorts directory in Application but this just a few<br>
> > > > > apps but no 'port' command. Any idea what is going on here?<br>
> > > > > Thanks,<br>
> > > > > Mark<br>
> > > > ><br>
> > > > ><br>
> > > > > On Mon, Jan 27, 2014 at 11:44 AM, Sean Farley <<br>
> > > > > <a href="mailto:sean.michael.farley@gmail.com">sean.michael.farley@gmail.com</a>> wrote:<br>
> > > > ><br>
> > > > >><br>
> > > > >> <a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a> writes:<br>
> > > > >><br>
> > > > >> > I think resolved it by getting rid of some stuff that macports<br>
> > > put in<br>
> > > > >> maybe<br>
> > > > >><br>
> > > > >> I just *completely* revamped the mpi ports in macports and would like<br>
> > > to<br>
> > > > >> know if these types of problems still exist.<br>
> > > > >><br>
> > > > >> > MPICH or libtool assumes certain files are there if other files<br>
> > > are<br>
> > > > >> 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">balay@mcs.anl.gov</a>><br>
> > > wrote:<br>
> > > > >> ><br>
> > > > >> >> On Mon, 27 Jan 2014, Jed Brown wrote:<br>
> > > > >> >><br>
> > > > >> >>> Mark Adams <<a href="mailto:mfadams@lbl.gov">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<br>
> > > MPICH.<br>
> > > > >> 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<br>
> > > macports<br>
> > > > >> >> install.<br>
> > > > >> >><br>
> > > > >> >> Satish<br>
> > > > >> >><br>
> > > > >> >><br>
> > > > >><br>
> > > > >><br>
> > > > ><br>
> > > ><br>
> > ><br>
> > ><br>
> ><br>
><br>
><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><span></span>Geoffrey Oxberry, Ph.D., E.I.T.<br><a href="mailto:goxberry@gmail.com" target="_blank">goxberry@gmail.com</a><br><span></span></div>
</div>