Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: bburky@bburky.com (Blake Burkhart)
Subject: [sup-talk] LibC on OpenBSD
Date: Sat, 15 Nov 2008 13:37:50 -0600	[thread overview]
Message-ID: <1226777116-sup-6508@ellipsis.bburky.com> (raw)

I had been still using an old version of sup for quite a while. It was either 0.5 or a dev version from between 0.5 and 0.6. I decided I actually needed to update it for once.

I tried downloading the tgz (I never can get gem to do what I want) of 0.6 but it didn't seem to work. I gave up on 0.6 and tried the version from git. Still problems.

When I ran it I got these errors:

$ ruby -I lib -w bin/sup 
/usr/local/lib/ruby/1.8/dl/import.rb:29:in `initialize': File not found (RuntimeError)
        from /usr/local/lib/ruby/1.8/dl/import.rb:29:in `dlopen'
        from /usr/local/lib/ruby/1.8/dl/import.rb:29:in `dlload'
        from /usr/local/lib/ruby/1.8/dl/import.rb:27:in `each'
        from /usr/local/lib/ruby/1.8/dl/import.rb:27:in `dlload'
        from ./lib/sup.rb:17
        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 bin/sup:9

Apparently it was breaking on loading LibC. I had no idea where LibC was supposed to be coming from so I searched my computer for it and finally found it called "libc.so.43.0"

I changed the "libc.so.6" part of lib/sup.rb:17 to "libc.so.43.0".

Basically, I was wondering if I had to do all that. Oh, and it does work perfectly fine now.
-- 
Blake Burkhart


             reply	other threads:[~2008-11-15 19:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 19:37 Blake Burkhart [this message]
2008-11-16  0:14 ` William Morgan
2008-11-16  0:42   ` Blake Burkhart
2008-11-16 17:08 ` marcus-sup

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=1226777116-sup-6508@ellipsis.bburky.com \
    --to=bburky@bburky.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