Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] install problems on ubuntu 10.10
Date: Sat, 17 Jul 2010 14:10:12 -0400	[thread overview]
Message-ID: <1279390136-sup-7516@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <AANLkTimoFaCUwRBX8u005SoygSgmlIYI72Ty2qLtLXAb@mail.gmail.com>

Excerpts from Daniel Goldin's message of Sat Jul 17 13:29:41 -0400 2010:

>     ERROR: Failed to build gem native extension.

To install the xapian gem, you'll need the xapian library and
development headers.  On my Ubuntu 10.10 box here, those are packages
named libxapian15 and libxapian-dev.

HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-07-17 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17 17:29 Daniel Goldin
2010-07-17 18:10 ` Ben Walton [this message]
2010-07-17 19:05 ` Mark Alexander

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=1279390136-sup-7516@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=sup-talk@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