I'm seeing a weird behavior with the xapian-full gem, and so is this guy. The installation claims it fails, but it actually succeeds. The spec file is not copied over after installation, so `gem list` doesn't show it, but if you require 'xapian' it actually does pick up the code, even after the failed installation.
Ideas? --- Begin forwarded message from Andrea Fazzi --- From: Andrea Fazzi <andrea.fa...@alcacoop.it> To: ruby-talk <ruby-t...@ruby-lang.org> Date: Mon, 25 Jan 2010 05:32:10 -0500 Subject: Re: Sup 0.10 released William Morgan wrote: > I'm pleased to announce the release of Sup 0.10. This version is > frickin' awesome because not only do we have Ruby 1.9 support, the > Xapian backend is now the default! The next version will discard Ferret > like a used rag. I had issues installing xapian-full gem on my ubuntu box running MRI ruby1.8. The installation fails building native extension even if it seems that all the C stuff get compiled correctly. BTW, I solved the issue in this way: sudo gem install xapian-full cd /usr/lib/ruby/gems/1.8/gems/xapian-full-1.1.3/ sudo rake build sudo mv xapian-full.gemspec ../../specifications/ and...@ubuntu-desktop:~$ irb irb(main):001:0> require 'rubygems' => true irb(main):002:0> require 'xapian' => true Thanks for this great software! Cheers, Andrea --- End forwarded message --- -- William <wmorgan-...@masanjin.net> _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel
