From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-devel mailing list <sup-devel@rubyforge.org>
Subject: [sup-devel] Fwd: Re: Sup 0.10 released
Date: Mon, 25 Jan 2010 16:19:13 -0500 [thread overview]
Message-ID: <1264454003-sup-9657@masanjin.net> (raw)
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.fazzi@alcacoop.it>
To: ruby-talk <ruby-talk@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/
andrea@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-sup@masanjin.net>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2010-01-25 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 21:19 William Morgan [this message]
2010-01-25 22:05 ` Rich Lane
2010-01-25 23:37 ` Rich Lane
2010-01-26 0:21 ` Mark Alexander
2010-01-26 0:35 ` Rich Lane
2010-01-26 13:22 ` William Morgan
2010-01-26 15:50 ` Nicolas Pouillard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1264454003-sup-9657@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox