From: Hamish D <dmishd@gmail.com>
To: Colin Yates <colin.yates@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Help - sup is garbling characters and chopping off the ends of lines
Date: Fri, 30 Sep 2011 19:58:40 +0100 [thread overview]
Message-ID: <CAOxvSbdS5fJEaXEYNivC83ws3VGFBuvdHWXRFnRFS45Lsg1v+g@mail.gmail.com> (raw)
In-Reply-To: <1317406494-sup-2375@os.Home>
> I cannot install the ncursesw gem due to a missing dependency - after install ruby1.9full and just about every ncurses package I could find I gave up :).
Do you get an error message about 'mkmf' - if so then you need to
install ruby-dev (or ruby1.9.1-dev) in order to get that. And make
sure you use gem1.9.1 if you are using ruby 1.9.
Anyway, glad to hear your main problem has been solved.
Hamish
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-09-30 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 21:39 Colin Yates
2011-09-30 18:03 ` Hamish D
2011-09-30 18:25 ` Colin Yates
2011-09-30 18:58 ` Hamish D [this message]
[not found] ` <1317409808-sup-8470@os.Home>
2011-10-01 12:50 ` Hamish D
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=CAOxvSbdS5fJEaXEYNivC83ws3VGFBuvdHWXRFnRFS45Lsg1v+g@mail.gmail.com \
--to=dmishd@gmail.com \
--cc=colin.yates@gmail.com \
--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