Anyone else upgrade to Mac OS X 10.6 (Snow Leopard)?

[Erik Bryn]

I went out to the Apple store this morning and picked up my copy of
Snow Leopard. Looks like my development environment is dead now after
the upgrade. I was using MacPorts for installing FreeTDS, and using
the Apple-provided MRI.

Anyone else trying to put together the pieces again? I'm trying to
rebuild FreeTDS, now using unixODBC (instead of the default iODBC
install with OS X)...

- Erik

[Erik Bryn]

Well, I was able to get FreeTDS installed from MacPorts, using OS X's iODBC. The ruby-odbc driver is segfaulting though...

- Erik

[Clifford Heath]

I don't have Snow Leopard, but I believe this blog contains what you
need to know

http://oleganza.tumblr.com/post/127709563/snow-leopard-with-legacy-macports-and-rubygems

Clifford Heath

[Ken Collins]

I did and had no troubles at all. The reason is that I always always
tell people to do this. Try to avoid "mixing" any native mac /usr lib/
binaries. ESPECIALLY WITH MACPORTS. because as soon as you do and you
upgrade... you just introduced dependency hell. I always install ruby
1.8.7/1.9.1 via MacPorts and always install everything needed for the
stack via it and hence into the opt directory. Because of that, I
installed Snow Leopard and had no issues, other than visor terminal [1].

I recommend that you built everything into /opt with MacPorts.
Remember to add the +odbc option to the freetds port so it links up
with unixODBC. You have to port install unixODBC first too.

- Ken

[1] http://www.metaskills.net/2009/8/18/visor-terminal-on-snow-leopard

[jordanyeo]

I'm segfaulting as well... anyone able to get this working?

[Erik Bryn]

I've tracked my original issue to Ruby-ODBC. You should just install Ruby, FreeTDS, and UnixODBC from Macports, then rebuild Ruby-ODBC. I had a functional system at one point with the Apple-provided Ruby, but I had trouble getting some other gems working... I'm in the process of switching completely over to a Macports-based install.

- Erik