From: gui-gui@netcourrier.com
To: "Jan Winkelmann" <subway.cookie@gmail.com>, supmua@googlegroups.com
Subject: Re: Re: sup broken with ruby 2.2?
Date: Wed, 4 Mar 2015 15:51:38 +0100 (CET) [thread overview]
Message-ID: <ea-mime-54f71bfa-7b3d-46c2f183@www-2.netcourrier.com> (raw)
In-Reply-To: <ec063081-e7a5-44fb-9250-e71694fb36a6@googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 2558 bytes --]
I get it to install by installing xapian-ruby first and then sup:
gem install xapian-ruby gpgme sup
--
Guillaume
---- Message d'origine ----
De : "Jan Winkelmann" <subway.cookie@gmail.com>
À : supmua@googlegroups.com
Objet : Re: sup broken with ruby 2.2?
Date : 04/03/2015 15:37:40 CET
Copie à : gui-gui@netcourrier.com
I have the same issue with sup-0.21:
[...]
Building native extensions. This could take a while...
/usr/bin/ruby mkrf_conf_xapian.rb
xapian: platform specific dependencies..
xapian: installing xapian-ruby..
ERROR: Error installing sup:
ERROR: Failed to build gem native extension.
Building has failed. See above output for more information on the failure.
rake failed, exit code 1
The patch posted has been merged before 0.21 so I don't think it helped. I'm on Arch Linux using Ruby 2.2.0.
Did anyone get it to work?
On Tuesday, January 6, 2015 at 11:13:26 AM UTC+1, gui...@netcourrier.com wrote:
Hello all,
I updated my system to ruby 2.2 and I can't get sup to work.
At first it didn't work so I figured I needed to recompile it, so I removed and reinstalled it. However, simply typing 'gem install sup' fails with this message:
Fetching: sup-0.20.0.gem (100%)
Building native extensions. This could take a while...
ERROR: Error installing sup:
ERROR: Failed to build gem native extension.
/usr/bin/ruby mkrf_conf_xapian.rb
xapian: installing xapian-ruby..
xapian: platform specific dependencies..
rake failed, exit code 1
Gem files will remain installed in /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.20.0 for inspection.
Results logged to /home/guiniol/.gem/ruby/2.2.0/extensions/x86_64-linux/2.2.0/sup-0.20.0/gem_make.out
I figured the problem was with xapian, so I tried to first install xapian-ruby and then sup, which works. However, sup doesn't launch. I get this error instead:
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- dl/import (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.20.0/bin/sup:111:in `<module:Redwood>'
from /home/guiniol/.gem/ruby/2.2.0/gems/sup-0.20.0/bin/sup:74:in `<top (required)>'
from /home/guiniol/.gem/ruby/2.2.0/bin/sup:23:in `load'
from /home/guiniol/.gem/ruby/2.2.0/bin/sup:23:in `<main>'
Has anyone else tried sup with ruby 2.2? Is there anything I can try to get it to work?
Cheers,
Guillaume
[-- Attachment #2: Type: text/html, Size: 3854 bytes --]
prev parent reply other threads:[~2015-03-04 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 10:13 gui-gui
2015-01-11 22:33 ` [sup] " Ruthard Baudach
2015-01-12 9:08 ` Gaute Hope
2015-01-12 21:05 ` Per Andersson
2015-03-04 14:37 ` Jan Winkelmann
2015-03-04 14:51 ` gui-gui [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=ea-mime-54f71bfa-7b3d-46c2f183@www-2.netcourrier.com \
--to=gui-gui@netcourrier.com \
--cc=subway.cookie@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