From: James Smith <james@abelsoninfo.com>
To: kgio@librelist.org
Subject: Re: Problem after installing kgio gem with ruby 2.0.0
Date: Mon, 28 Jul 2014 13:47:04 +0100 [thread overview]
Message-ID: <CANRV1hw9FpP-kUwC04yc7-a67n72=XwVcP2fQ2oKYtYPHofsiw@mail.gmail.com> (raw)
In-Reply-To: 20140725180007.GA27611@dcvr.yhbt.net
Hi Eric,
Ruby and RubyGems were built from source.
Unfortunately I didn't have time to be more thorough (had to get the server
up and running ASAP) but a whole bunch of other Gems (including Nokogiri,
which I think uses C extensions no?) were installing fine. Just thought it
would be useful to report what I'd found to the mailing list.
Thanks,
James.
On 25 July 2014 19:00, Eric Wong <normalperson@yhbt.net> wrote:
> James Smith <james@abelsoninfo.com> wrote:
> > Here are the environment details:
> > OS: Ubuntu Server 12
> > Ruby: 2.0.0-p247
> > Gem: 1.8.24
> >
> > I got around this problem by upgrading to Ruby 2.1.2p95. I didn't try
> > versions between 2.0.0-p247 and 2.1.2p95 so can't say when the problem
> goes
> > away.
>
> Hi James, thanks for the report.
> How did you install build and install Ruby + RubyGems?
>
> Can you reproduce the problem on other C extension gems with
> ruby 2.0.0-p247 and RubyGems 1.8.24?
>
> I suspect this to be a problem with the Ruby/RubyGems installation
> itself and perhaps a bug of your distribution/build/install tools.
>
> Since you have no problem with Ruby 2.1.2p95, I do not think it is
> a problem specific to kgio.
>
--
James Smith
Abelson Info
Barley Mow Centre
10 Barley Mow Passage
London W4 4PH
[t] 020 3735 5322
[e] james@abelsoninfo.com
prev parent reply other threads:[~2014-07-28 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 9:16 Problem after installing kgio gem with ruby 2.0.0 James Smith
2014-07-25 18:00 ` Eric Wong
2014-07-28 12:47 ` James Smith [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
List information: https://yhbt.net/kgio/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANRV1hw9FpP-kUwC04yc7-a67n72=XwVcP2fQ2oKYtYPHofsiw@mail.gmail.com' \
--to=james@abelsoninfo.com \
--cc=kgio@librelist.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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/kgio.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).