Comments on: libxml-ruby problems on Mac OS X

By: jacob

jacob — Wed, 08 Apr 2009 12:23:04 +0000

Glad I could help!

By: Andy Mendelsohn

Andy Mendelsohn — Wed, 08 Apr 2009 12:18:59 +0000

Thanks for that. You’ve saved me a lot of grief!

I’ve hit this problem before and hassle factor caused me to knock it back till a later time – that later time came when I got the dreaded bus error today.

sudo port install libxml2 +universal
+
sudo bash
ARCHFLAGS=’-arch i386 -I /opt/local/include/libxml2′ gem install -r libxml-ruby — –build-flags –with-opt-lib=/opt/local/lib

And all’s sweet and dandy now!

By: jacob

jacob — Sat, 07 Mar 2009 09:57:12 +0000

Hi Charlie,

Thanks for clearing that up; abusing ARCHFLAGS like I did just seems wrong, so I think I prefer building libxml2 as a universal binary like you suggest.

By: Charlie

Charlie — Sat, 07 Mar 2009 09:39:34 +0000

Hey Jacob,

Thanks for posting this – I’m actually trying to fix it now.

When a gem extension is built, it picks up the cflags and ldflags that were used to build Ruby itself. So on OS X 10.5:

ruby –version
ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
ruby -rrbconfig -e ‘puts Config::CONFIG["CFLAGS"]‘ -arch ppc -arch i386 -Os -pipe -fno-common
arch ppc -arch i386 -Os -pipe -fno-common

And thus the inclusion of ppc. Seems like the workaround is the one you figured out, or building libxml2 as a universal binary:

sudo port install libxml2 +universal