From: John Toohey <jt@parspro.com>
To: sup-talk@rubyforge.org
Subject: [sup-talk] Problems installing Sup on OSX 10.6
Date: Fri, 3 Jun 2011 17:16:07 -0400 [thread overview]
Message-ID: <BANLkTinHtAL4_TqSYeLxxQPfOF6j4W0tBQ@mail.gmail.com> (raw)
Just found this project, but having difficulty installing Sup. On OSX
I get the following :-
ERROR: Error installing sup:
ERROR: Failed to build gem native extension.
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby 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.
Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
--with-ncurseswlib
--without-ncurseswlib
--with-pdcurseslib
--without-pdcurseslib
extconf.rb:46: ncurses library not found (RuntimeError)
Gem files will remain installed in
/Library/Ruby/Gems/1.8/gems/ncursesw-1.2.4.3 for inspection.
Results logged to /Library/Ruby/Gems/1.8/gems/ncursesw-1.2.4.3/gem_make.out
Gem version is 1.3.5, and Ruby is ruby 1.8.7 (2009-06-12 patchlevel
174) [universal-darwin10.0]
My /opt/local/lib has libncurses installed, but being new to Ruby, I
am not sure how Ruby searches for libraries. Any help would be
appreciated.
--
~JT
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2011-06-03 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 21:16 John Toohey [this message]
2011-06-04 1:40 ` Andrew Farrell
2011-06-04 16:12 ` John Toohey
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=BANLkTinHtAL4_TqSYeLxxQPfOF6j4W0tBQ@mail.gmail.com \
--to=jt@parspro.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