From: william.betts@gmail.com (William Betts)
Subject: [sup-talk] Error when running sup
Date: Mon, 13 Aug 2007 10:55:45 -0500 [thread overview]
Message-ID: <17b80a160708130855u34a2624fga748c4bd22906232@mail.gmail.com> (raw)
Hello,
I just installed sup using gem install sup -y after it finished
installing I tried to run "sup" and I received the following errors.
/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:21:in
`require__': no such file to load -- iconv (LoadError)
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:21:in
`require'
from /usr/local/lib/ruby/gems/1.8/gems/sup-0.1/lib/sup/message.rb:3
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require__'
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.rb:208
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`require__'
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/bin/sup:7
from /usr/local/bin/sup:18:in `load'
from /usr/local/bin/sup:18
uname -a output:
FreeBSD <hostname_removed> 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan
12 10:40:27 UTC 2007
root at dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Any help would be appreciated.
Thank You,
William
next reply other threads:[~2007-08-13 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 15:55 William Betts [this message]
2007-08-13 22:10 ` 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=17b80a160708130855u34a2624fga748c4bd22906232@mail.gmail.com \
--to=william.betts@gmail.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