From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup and OpenBSD
Date: Wed, 26 Nov 2008 15:40:23 -0800 [thread overview]
Message-ID: <1227742378-sup-558@entry> (raw)
In-Reply-To: <98f5a8830811260948v1fbfd41ay62524d78e57b47cc@mail.gmail.com>
Reformatted excerpts from Nick Guenther's message of 2008-11-26:
> The problem here is that you are asking for libc.so.6 which OpenBSD
> doesn't have (on my 4.3 system I see ["/usr/lib/libc.so.41.0",
> "/usr/lib/libc.so.43.0"]).
Someone else just reported this problem too. I wonder whether the best
solution is your patch (remove the .6) or the patch I was thinking of,
where we special-case BSD to look for libc.so.43. Does anyone have any
suggestions?
> I installed the OpenBSD ruby-ncurses package instead and hoped all was
> well. I am just learning Ruby, but the fact that sup gets past
> `require 'ncurses'` means that ncurses should be installed right?
I... think so. What's your TERM environment variable set to? Do other
(color!) ncurses programs work?
> form_wrap.c: In function `field_check':
> form_wrap.c:1147: error: `true' undeclared (first use in this function)
Do you have both ncurses and ruby development libraries installed? I
know what they are in Linux world but not in BSD land.
> Anyway, it shouldn't matter that the gem can't install because the
> ncurses.rb I have installed in site_ruby is newer than the ncurses.rb
> from the gem, judging from the version line. I don't know what to make
> of this since at all. I'm not familiar with Ruby yet but if you could
> point me at a right direction I will probably be able to figure this
> out.
Yeah, I would ignore the gem issue for now. I suspect that at this point
it's a matter of tricking the 1970's technology that is ncurses into
displaying color on your particular environment, by trying different
TERMs and terminal emulators.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-11-26 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 17:48 Nick Guenther
2008-11-26 23:40 ` William Morgan [this message]
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=1227742378-sup-558@entry \
--to=wmorgan-sup@masanjin.net \
/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