From: Ben Bleything Date: 2010-06-18T04:34:54+09:00 Subject: Re: Dear gem: still no zlib. On Thu, Jun 17, 2010 at 12:16 PM, Dave Howell wrote: > Um, it's COMPLETELY SnowLeopard's fault. I *am* using the stock Ruby, > which changed from 32-bit in Leopard to 64-bit in SnowLeopard. Ah, okay. So you did an upgrade install, and are now surprised that sweeping architectural changes affected software you already had installed. > Thus rendering every single Ruby program I had non-functional, since > all my gems were 32-bit. And my PostgreSQL. And lots and lots of other > stuff. Including a bunch of system OSAXen that Apple didn't upgrade to > 64-bit. Upgrade installs aren't worth it, particularly from 10.5 -> 10.6. I know that sucks to hear, but doing a clean install *will* fix your problems. > I had to actually go back and pull my own Ruby off my backups so that > I had a 32-bit Ruby just so I could get work done. Perhaps an expedient solution, but not a very clean one. From your other post: > $ file /opt/local/lib/libz.dylib > libz.dylib: Mach-O 64-bit dynamically linked shared library x86_64 > So I have a 64-bit libz.dylib. Gem is ignoring my /opt tree. Why are you using macports for this? Every additional piece you add is making solving your problem so much more complicated. You already have a universal libz: $ file /Developer/SDKs/MacOSX10.6.sdk/usr/lib/libz.dylib /Developer/SDKs/MacOSX10.6.sdk/usr/lib/libz.dylib: Mach-O universal binary with 3 architectures /Developer/SDKs/MacOSX10.6.sdk/usr/lib/libz.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library stub x86_64 /Developer/SDKs/MacOSX10.6.sdk/usr/lib/libz.dylib (for architecture i386): Mach-O dynamically linked shared library stub i386 /Developer/SDKs/MacOSX10.6.sdk/usr/lib/libz.dylib (for architecture ppc7400): Mach-O dynamically linked shared library stub ppc Bottom line is, your environment is broken. Based on all of the screwing around you've done to fix the situation, I don't know how to recommend you clean it up other than suggesting you do a clean install... which again, I know sucks. But these things *do* work fine on Snow Leopard, using the stock ruby, without macports. You just need to start from a clean spot, which you didn't do when you did the in-place upgrade. Ben