From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] Errors installing ncursesw
Date: Wed, 10 Nov 2010 12:07:40 +0000 [thread overview]
Message-ID: <1289390629-sup-7999@blake> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
Given the other thread on how ncursesw cures those odd character strings, I've revisited this myself and I wonder if I could get suggestions.
>>>>
user@computer:$ sudo gem install ncursesw
Building native extensions. This could take a while...
ERROR: Error installing ncursesw:
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.8 extconf.rb
checking for unistd.h... yes
checking for locale.h... yes
checking for ncurses.h... yes
checking for wmove() in -lncursesw... no
checking for wmove() in -lpdcurses... no
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers. Check the mkmf.log file for more
details. You may need configuration options.
<<<<
Can anyone tell me where mkmf.log will be? Not in the directory where I ran gem install.
I'm on Ubuntu 9.04 -- is that the problem?
--
It is easier for a camel to pass through the eye of a needle if it is
lightly greased.
-- Kehlog Albran, "The Profit"
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-11-10 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 12:07 Shadowfirebird [this message]
2010-11-10 15:04 ` William Morgan
2010-11-10 15:46 ` Mark Alexander
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=1289390629-sup-7999@blake \
--to=shadowfirebird@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