From: raymond@raykroeker.com (Raymond Kroeker)
Subject: [sup-talk] Sup on Ubuntu
Date: Tue, 16 Oct 2007 19:39:28 -0700 [thread overview]
Message-ID: <fa14d5020710161939w3ac2073dh8b706137082888b3@mail.gmail.com> (raw)
Hi All,
I've a problem running sup. I downloaded/compiled/installed ruby 1.8.5.
I downloaded/installed gems 0.9.4. I installed the sup gem and its
dependencies. When I run sup I get the included warnings/errors.
I _think_ my problem has something to do with my potential confusion
between ncurses and curses. I've installed the libraries via apt; and can
load ncurses (see below) but curses cannot be loaded.
Any help would be appreciated.
user at host:~$ sup
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:34: warning: already
initialized constant VERSION
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:36: warning: already
initialized constant BASE_DIR
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:37: warning: already
initialized constant CONFIG_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:38: warning: already
initialized constant SOURCE_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:39: warning: already
initialized constant LABEL_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:40: warning: already
initialized constant PERSON_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:41: warning: already
initialized constant CONTACT_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:42: warning: already
initialized constant DRAFT_DIR
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:43: warning: already
initialized constant SENT_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:44: warning: already
initialized constant LOCK_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:45: warning: already
initialized constant SUICIDE_FN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:47: warning: already
initialized constant YAML_DOMAIN
/usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:48: warning: already
initialized constant YAML_DATE
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no such file to load -- curses (LoadError)
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
from /usr/local/lib/ruby/gems/1.8/gems/sup-0.1
/lib/sup/textfield.rb:1
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`gem_original_require'
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require'
from /usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup.rb:217
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
`gem_original_require'
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require'
from /usr/local/lib/ruby/gems/1.8/gems/sup-0.1/bin/sup:7
from /usr/local/bin/sup:16:in `load'
from /usr/local/bin/sup:16
I also have this issue if I start irb and type:
user at host:~$ irb
irb(main):001:0> require 'rubygems'
=> true
irb(main):002:0> require 'curses'
LoadError: no such file to load -- curses
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require'
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require'
from (irb):2
irb(main):003:0> require 'ncurses'
=> true
irb(main):004:0> quit
--
---------------------------------------------------------
Raymond Kroeker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071016/15204523/attachment-0001.html
next reply other threads:[~2007-10-17 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 2:39 Raymond Kroeker [this message]
2007-10-27 1:39 ` William Morgan
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=fa14d5020710161939w3ac2073dh8b706137082888b3@mail.gmail.com \
--to=raymond@raykroeker.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