On Feb 27, 1:43 pm, Calvin Bascom <[EMAIL PROTECTED]> 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. Thanks, T. _______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
