From: Peng Yu <pengyu.ut@gmail.com>
To: None <supmua@googlegroups.com>
Subject: xapian problem (install sup)
Date: Wed, 18 Mar 2015 12:03:57 -0500 [thread overview]
Message-ID: <CABrM6w=1f+EjqFQt=d2i69haYQjZa0iX++OJVfPbUHLw8BMV-A@mail.gmail.com> (raw)
I have the following problem, when I install sup. Does anybody know
what is wrong? Thanks.
/tmp/ruby-2.0.0-p643$ sudo gem install sup
Fetching: ncursesw-1.4.9.gem (100%)
Building native extensions. This could take a while...
Successfully installed ncursesw-1.4.9
Fetching: rmail-sup-1.0.1.gem (100%)
Successfully installed rmail-sup-1.0.1
Fetching: highline-1.7.1.gem (100%)
Successfully installed highline-1.7.1
Fetching: trollop-2.1.2.gem (100%)
Successfully installed trollop-2.1.2
Fetching: lockfile-2.1.3.gem (100%)
Successfully installed lockfile-2.1.3
Fetching: mime-types-1.25.1.gem (100%)
Successfully installed mime-types-1.25.1
Fetching: locale-2.1.0.gem (100%)
Successfully installed locale-2.1.0
Fetching: chronic-0.9.1.gem (100%)
Successfully installed chronic-0.9.1
Fetching: unicode-0.4.4.2.gem (100%)
Building native extensions. This could take a while...
Successfully installed unicode-0.4.4.2
Fetching: sup-0.21.0.gem (100%)
Building native extensions. This could take a while...
ERROR: Error installing sup:
ERROR: Failed to build gem native extension.
/usr/local/bin/ruby mkrf_conf_xapian.rb
xapian: installing xapian-ruby..
xapian: platform specific dependencies..
Building native extensions. This could take a while...
Gem files will remain installed in
/usr/local/lib/ruby/gems/2.0.0/gems/sup-0.21.0 for inspection.
Results logged to
/usr/local/lib/ruby/gems/2.0.0/gems/sup-0.21.0/ext/gem_make.out
--
Regards,
Peng
next reply other threads:[~2015-03-18 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 17:03 Peng Yu [this message]
2015-03-18 17:09 ` [sup] " Mark Alexander
2015-03-18 17:41 ` Peng Yu
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='CABrM6w=1f+EjqFQt=d2i69haYQjZa0iX++OJVfPbUHLw8BMV-A@mail.gmail.com' \
--to=pengyu.ut@gmail.com \
--cc=supmua@googlegroups.com \
/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