From: Ruthard Baudach <ruthard.baudach@web.de>
To: supmua <supmua@googlegroups.com>
Subject: Re: [sup] sup broken with ruby 2.2?
Date: Sun, 11 Jan 2015 23:33:25 +0100 [thread overview]
Message-ID: <1421014626-sup-9934@ruthard-lappi> (raw)
In-Reply-To: <ea-mime-54abb545-139f-5185130b@www-1.netcourrier.com>
It hit me, too.
The problem seems to be a deprecated DL module, that is
substituted by Fiddle and removed from Ruby 2.2. (remember the
deprecation notice when sup started?)
Assuming that the API of fiddle is the same as of DL, I replaced 'dl' by
'fiddle' and it seems to work:
Locate your master sup script -- it should live in sup's bin/ directory,
if you installed sup via `gem install` this should be
`$HOME/.gem/ruby/2.2.0/gems/sup-0.20.0/bin/sup` for a current sup and
ruby install
open this file in the editor of your choice.
line 111 has to be changed from
require 'dl/import'
to
require 'fiddle/import'
and line 113 from
extend DL.const_defined?(:Importer) ? DL::Importer : DL::Importable
to
extend Fiddle::Importer
Sorry to Gaute and all developers for not providing a patch, but
a) I'm not really shure this will work, someone should probably skim the
documentation of ruby 2.1.5 dl/import and ruby 2.2.0 fiddle/import
b) I'm still not really acquainted with git.
Best regards,
Ruthard
>== Auszüge aus der Nachricht von gui-gui vom 2015-01-06 11:13:
> 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
>
--
Emails are postcards.
Put them in an envelope,
Sign and encrypt them!
My PGP-Id: 0xAC5AC6C2
next prev parent reply other threads:[~2015-01-11 22:33 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 ` Ruthard Baudach [this message]
2015-01-12 9:08 ` [sup] " Gaute Hope
2015-01-12 21:05 ` Per Andersson
2015-03-04 14:37 ` Jan Winkelmann
2015-03-04 14:51 ` gui-gui
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=1421014626-sup-9934@ruthard-lappi \
--to=ruthard.baudach@web.de \
--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