- Round 3 lingers…
- Round 2 begins
- On losing hair
- Solving the World’s Fluffy Tailed Rodent Problem
- Chemo: day 5 (belated)
Polluting the internet since 2004
The inevitable happened today. Mountain Lion was installed in a couple of different places. Unfortunately one of those places was at work and on a development machine before we had a chance to test out Mountain Lion compatability. Predictably, issues arose. Not surprisingly, at least to me, Homebrew has the biggest issue, and an issue based on its core philosophy.
Prior to Mountain Lion the Xcode Command Line Tools could be downloaded separately from Xcode. This saved many of us the bandwidth and storage space required to install Xcode. As of the time of this writing I can only find the individually downloadable Command Line tools available for regular old Lion.
So that means a download of Xcode is required. Dag nabbit.
After downloading and installing Xcode open Xcode and go in to its Preferences, click on the Downloads tab and install the Command Line Tools.
Update: As noted by Patrick Quinn-Graham in the comments below, the Command Line Tools are now showing up in Apple’s Developer portal. I recommend grabbing that if you don’t need the full Xcode suite.
After that is done head to the command line and accept the command line tools usage agreement.
Press space a few times to get through the whole thing and then type “accept” when it prompts you to. This provided a fun distraction for both Homebrew and MacPorts as the errors delivered because of needing to accept the usage agreement in no way point to the root cause of the errors. And to add insult to injury this was not needed on every system that I’ve had to manage. I found this by blind luck.
We’re done with Xcode. We’re now ready to compile applications on Mountain Lion.
MacPorts survived the upgrade just fine. MySQL, PHP and Apache were all running when Mountain Lion restarted. But just to be safe I updated MacPorts.
After the update almost everything that I had installed became listed as “outdated”. So, everything needed upgrading… :sigh:
But, all in all, done and done. Ok, eventually it was done after 6 hours of compiling.
Homebrew was harder. Homebrew’s base philosophy, a philosophy that everyone loves about it (well, except for me) is that it uses already installed system libraries to run. Today that proved to be a bad thing.
Apple removed support for X11 in Mountain Lion. This means that anything that was linking to a library that was supplied by X11 would now complain and die. This meant our custom compiled version of PHP at work. dylibs were missing which prevented PHP from running and header files could not be found which prevented an update to PHP from compiling.
The Homebrew folks saw it coming a while back. There are pull requests and changes in branches that deal with this issue. However the best I can tell not all of that has made it in to master and its still not ready to go.
There is a work around, and it relies on installing XQuartz to provide the required X11 libraries. This may not be required for everyone, but for those of us that run specific versions of software it means a headache. In our case, for PHP, it meant that libraries required for font and image handling were missing. And these are just the errors that came up first. I’m not sure how many other things that X11 provided were waiting to error out should we have tried to link in the parts as we found the errors.
First, download and install XQuartz. After doing that symlink it in to where Homebrew expects X11 to be. We had folder there, presumably left over from the upgrade.
Now, since this was an OS upgrade all of the config and ini files have been renamed and replaced. This means that the Apache conf and PHP ini files needed replacing. Fortunately for us we had a custom Homebrew Formula that handled this portion of the environment for us. So we just had to uninstall and reinstall that Formula to re-configure Apache and PHP how we had it. Your setup will of course be different.
So, overall, while my total time spent troublehsooting, updating and fixing a Homebrew install today took up a little more than 4 hours of my day, it was fixed and working.
While I’m still pissed at Homebrew for taking more of my brainpower today its 4 hour investment is a bit shorter than the time it took MacPorts to get up to date.
I have to say, though, that despite the longer compile time to update MacPorts I still prefer it for the sheer fact that it didn’t force me to pay attention to it to upgrade to ML. I decided to pay attention to it (and would have had to eventually anyway). I was able to address MacPorts on my time, not because something was horribly broken.
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
I just did this
BREWDOG, July 27, 2012 6:07 am | permalink
The download of the command line tools is here: https://developer.apple.com/downloads/index.action
Look for “Command line tools 10.8 for Xcode – Late July 2012″. It’s also available in the Xcode 4.4 chunk as “Xcode 4.4 Command Line Tools for OS X 10.8″
Patrick Quinn-Graham, July 27, 2012 8:30 am | permalink
Great! Nice to see that it was just lagging behind a little bit and not a change in policy to force more Xcode downloads.
Dude, very awesome writeup on how to navigate this transition!! Thanks for sharing!!!
Rollin, July 31, 2012 5:04 pm | permalink
XCode was in the wrong place for me this is what helped me out sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
I was using macports in OS X Lion, before Homebrew. Of course, the later made my life easier. But didn’t saw that coming (ML without X11).
Now I realize why my friend always suggested to fall in love with his favorite Arch Linux and the most popular apt-get package manager!! 😛
[…] MacPorts, Homebrew and Mountain Lion → 6 seconds ago […]
July 26, 2012 | 11:40 pm
[…] prefer Homebrew to MacPorts, but caveat emptor. […]
February 23, 2013 | 11:19 am
Comments are closed