From: John Bent <johnbent@lanl.gov>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup install error
Date: Wed, 03 Mar 2010 15:25:08 -0700 [thread overview]
Message-ID: <1267655048-sup-9690@tangerine.lanl.gov> (raw)
In-Reply-To: <1267654880-sup-4875@zyrg.net>
Excerpts from Rich Lane's message of Wed Mar 03 15:23:06 -0700 2010:
> Excerpts from John Bent's message of 2010-03-01 16:26:09 -0500:
> > I've been using an old PowerPC Mac. I got a new Intel one running
> > Leopard (10.6.2) but got an error trying to install sup. Everything is
> > a fresh install. The only thing I've done is install the Xcode tools.
> > The error (below sig) looks like a problem with ncurses. Looking around
> > at the mkmf.log file (attached), I see more issues with curses: no
> > wmove(), no libpdcurses.
> >
> > The ruby installed is 1.8.7. gem is 1.3.1.
> >
> > I recreated this by copying the little test program with the wmove() in
> > it. When I tried to build it with -lncursesw, it failed because that
> > lib doesn't exist but it did work with -lncurses (without the 'w'). So
> > I just made a symlink:
> >
> > guava:/usr/lib>ln -s /usr/lib/libncurses.dylib /usr/lib/libncursesw.dylib
> >
> > That works. Now gem install sup works. But I'm not sure that's the
> > best fix. Anyway, it looks like the problem is in gem install ncursesw
> > and not in gem install sup but I thought you might like to know about
> > this.
> >
> > Thanks,
> >
> > John
> >
> > guava:~>gem install sup
> > Building native extensions. This could take a while...
> > ERROR: Error installing sup:
> > ERROR: Failed to build gem native extension.
> >
> > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
> > extconf.rb install sup
> > 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.1 for inspection.
> > Results logged to /Library/Ruby/Gems/1.8/gems/ncursesw-1.2.4.1/gem_make.out
>
> I'm thinking about changing the gem dependency from ncursesw back to
> plain ncurses to avoid these install failures. Anyone have thoughts on
> this?
>
+1 :)
John
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-03-03 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 21:26 John Bent
2010-03-01 21:57 ` John Bent
2010-03-01 23:50 ` John Bent
2010-03-03 22:23 ` Rich Lane
2010-03-03 22:25 ` John Bent [this message]
2010-03-04 2:10 ` Mark Alexander
2010-03-04 11:45 ` Helge Titlestad
2010-03-04 16:59 ` Rich Lane
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=1267655048-sup-9690@tangerine.lanl.gov \
--to=johnbent@lanl.gov \
--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