[libxml-devel] xml/libxml won't load in OS X 10.5.2 Leopard

[Trans]

On Wed, Mar 26, 2008 at 12:12 AM, Stephen Bannasch
<stephen.bannasch at deanbrook.org> wrote:
> At 6:59 PM -0800 2/27/08, Trans wrote:
>  >On Feb 27, 1:43 pm, Calvin Bascom <cbas... at revasystems.com> wrote:
>  >> I ran into this as well installing the 0.5.3 gem on both CentOS and
>  >> Fedora platforms.  To get it working I had to rebuild the .so file
>  >> manually after the gem install:
>  >>
>  > > cd /usr/local/lib/ruby/gems/1.8/gems/libxml-ruby-0.5.3
>  > > ruby xml/libxml/extconf.rb
>  >> make
>  >> make install
>  >> make distclean
>  >>
>  >> The make install step copied the libxml_so.so file to the correct
>  >> directory whereas the gem installation didn't for some reason.  Don't
>  >> know what causes this, but it at least worked for me after doing the above.
>  >
>  >I'm glad someone has tried that new gem out finally -- this is a
>  >"beta" release (obviously).
>  >
>  >In contrast to setup.rb, the Gem is not suppose to copy the .so,
>  >rather the loadpath should point to it. (At least that's what Eric
>  >Hodel told me was the proper way). Interestingly, you used make
>  >install to copy the .so over into the proper lib/ directory.
>  >
>  >I figured out the problem with the gem. In the gemspec, the extensions
>  >field isn't getting set properly, so it can't find the extconf.rb.
>  >Will fix shortly.
>
>  I just installed the 0.5.3 gem on Leopard 10.5.2 yesterday and it still has the same problem -- but the solution described above doesn't work ...

Just released 0.5.4 that should fix this problem.

>  On my system the gem is located here:
>
>   /Library/Ruby/Gems/1.8/gems/libxml-ruby-0.5.3
>
>  The location of extconf.rb is here:
>
>   ./ext/libxml/extconf.rb
>
>  Executing that file produces this error:
>
>  $ ruby ext/libxml/extconf.rb
>  checking for socket() in -lsocket... *** ext/libxml/extconf.rb failed ***
>  Could not create Makefile due to some reason, probably lack of
>  necessary libraries and/or headers.  Check the mkmf.log file for more
>  details.  You may need configuration options.

Does the mkmf.log provide any clues?

T.