From: Ian Smith <ismith@MIT.EDU>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] utf8 support on Ubuntu Karmic
Date: Sun, 11 Apr 2010 19:30:06 -0400 [thread overview]
Message-ID: <1271028514-sup-7691@baad> (raw)
In-Reply-To: <o2q3c5cf5261004111608q9ac4dd89v1e8c9cf3bf0ee9b3@mail.gmail.com>
Hi Brian - I believe before installing the ncursesw gem, you need to install
libncurses-ruby (using aptitude). You may also need libncursesw-dev; I've got
both of those installed on my machine, and I'm honestly not sure which one is
necessary.
Ian
Excerpts from Brian May's message of Sun Apr 11 19:08:28 -0400 2010:
> Hello,
>
> I have been trying out sup, and rather like it. Unfortunately, it
> seems very easy
> to crash :-(
>
> First things though, how do I get utf8 support working properly?
>
> [Mon Apr 12 08:52:00 +1000 2010] No 'ncursesw' gem detected. Install
> it for wide character support.
>
> How do I install this on a Ubuntu Karmic system?
>
> I tried:
>
> brian@aquitard:~/tree/sup$ sudo gem install ncursesw
> Building native extensions. This could take a while...
> ERROR: Error installing ncursesw:
> ERROR: Failed to build gem native extension.
>
> /usr/bin/ruby1.8 extconf.rb
> extconf.rb:23:in `require': no such file to load -- mkmf (LoadError)
> from extconf.rb:23
>
>
> Gem files will remain installed in
> /var/lib/gems/1.8/gems/ncursesw-1.2.4.1 for inspection.
> Results logged to /var/lib/gems/1.8/gems/ncursesw-1.2.4.1/gem_make.out
>
>
> Thanks
--
Ian Smith
ismith@mit.edu
http://www.bostonaccess.org
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-04-11 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 23:08 Brian May
2010-04-11 23:30 ` Ian Smith [this message]
2010-04-12 0:10 ` Brian May
2010-04-12 0:15 ` Rich Lane
2010-08-06 3:54 ` Brian May
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=1271028514-sup-7691@baad \
--to=ismith@mit.edu \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox