Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed
From: Peng Yu <pengyu.ut@gmail.com>
To: Mark Alexander <marka@pobox.com>, None <supmua@googlegroups.com>
Subject: Re: [sup] xapian problem (install sup)
Date: Wed, 18 Mar 2015 12:41:16 -0500	[thread overview]
Message-ID: <CABrM6wks9y-_z9Sm4qGaZz5Xy8d9z79jVkw5BGdFDeMx+g44jw@mail.gmail.com> (raw)
In-Reply-To: <1426698455-sup-1324@t60p>

On Wed, Mar 18, 2015 at 12:09 PM, Mark Alexander <marka@pobox.com> wrote:
> Excerpts from Peng Yu's message of 2015-03-18 13:03:57 -0400:
>> ERROR:  Error installing sup:
>>     ERROR: Failed to build gem native extension.
>>
>>     /usr/local/bin/ruby mkrf_conf_xapian.rb
>> ...
>> Results logged to
>> /usr/local/lib/ruby/gems/2.0.0/gems/sup-0.21.0/ext/gem_make.out

The log file is not helpful.

~$ cat  /usr/local/lib/ruby/gems/2.0.0/gems/sup-0.21.0/ext/gem_make.out
/usr/local/bin/ruby mkrf_conf_xapian.rb
xapian: installing xapian-ruby..
xapian: platform specific dependencies..
Building native extensions.  This could take a while...

> You'll need to take a look at that log file to figure this out.
> But I've run into this before, and the first problem I had was that
> I didn't have g++ installed.

~$ g++ --version
g++ (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

-- 
Regards,
Peng


      reply	other threads:[~2015-03-18 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 17:03 Peng Yu
2015-03-18 17:09 ` [sup] " Mark Alexander
2015-03-18 17:41   ` Peng Yu [this message]

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=CABrM6wks9y-_z9Sm4qGaZz5Xy8d9z79jVkw5BGdFDeMx+g44jw@mail.gmail.com \
    --to=pengyu.ut@gmail.com \
    --cc=marka@pobox.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