I thought I'd do an SVN update of a project I collaborated with a friend on a few months ago. Ha.
Some MacOS system update has changed the berkeley db library version.
I get the latest subversion. No gcc. Doh.
I read web advice on how to get subversion via darwinports. Hmm, I have darwinports.
First advice includes telling darwinports to update itself. Hokay. Darwinports goes and spends umpteen minutes and megabytes syncing its whole local repository *before* getting to the part of the script that tells it to fail due to no gcc. *headdesk*
So, here I am downloading Xcode2.2 from the Apple Developer Site, having failed to find gcc binaries in any easy-to-grok form. Found plenty of pointers to using darwinports to get gcc. Yeah, like that works if you don't already HAVE gcc. Gah.
Well, I needed to set up a Rails dev environment on my desktop anyway, and I'll need gcc for that, so whatever. But, but, but… GNAR!
Why does this seem 'hard', when getting the bootstrap gcc off the Sun Catalyst CD and then compiling gcc for Solaris was 'easy'? Later on, sunsite.unc.edu took pretty much *all* the work out of it. But this, this still seems like a pain in the ass.
“Soon, soon, my pretties, once I have built the finest alligator gun in the world, I shall begin on my original objective to survey for drainage points in the swamp. (pause) Once I have assembled the ACME Finest Alligator Gun in the World Kit… (pause) Once I have forged the barrel for the ….(pause) Once I have smelted the ore to cast the pig iron to forge the barrel for… oh, look. A meteor. Well, *that's* lucky. Where was I going to *get* the ore to smelt to cast the” ****SPLAT****
Relentless Inquiry 
Leave a Reply