Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Mark Alexander <marka@pobox.com>
To: Shadowfirebird <shadowfirebird@gmail.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Errors installing ncursesw
Date: Wed, 10 Nov 2010 10:46:53 -0500	[thread overview]
Message-ID: <1289403600-sup-5733@r61> (raw)
In-Reply-To: <1289390629-sup-7999@blake>

Excerpts from Shadowfirebird's message of Wed Nov 10 07:07:40 -0500 2010:
> Can anyone tell me where mkmf.log will be?  Not in the directory where I ran gem install.

If you run 'gem env' you'll see something like this:

  ...
  - GEM PATHS:
     - /var/lib/gems/1.8
  ...

Then in that directory you'll see a directory called 'gems' that will
contain the source directories for the various gems.  mkmf.log should
be in the directory containing the failing gem.  If you look at the
log, there will often be a clue pointing to a missing header file or
library.  To fix this, you'll typically have to install some kind of
development library.  For example, on Ubuntu, if you're getting
failures installing the ncursesw gem, you'll probably have to install
the libncursesw5-dev package.  You can find a list of candidate
packages by doing 'aptitude search ncursesw'.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      parent reply	other threads:[~2010-11-10 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 12:07 Shadowfirebird
2010-11-10 15:04 ` William Morgan
2010-11-10 15:46 ` Mark Alexander [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=1289403600-sup-5733@r61 \
    --to=marka@pobox.com \
    --cc=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