All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nate Bargmann <n0nb@networksplus.net>
To: linux-hams@vger.kernel.org
Subject: Re: installing Predict on a RedHat 7.3 box , no go :^(
Date: Sun, 15 Dec 2002 20:02:07 -0600	[thread overview]
Message-ID: <20021216020207.GJ448@localhost> (raw)
In-Reply-To: <200212151628.02870.n7bfs@qwest.net>

* Douglas Cole <n7bfs@qwest.net> [2002 Dec 15 18:35 -0600]:
> [root@n7bfs predict-2.2.1]# ./configure
> One moment please... installer.c:16:20: curses.h: No such file or directory
> Compilation failed.  Are you sure you have a C compiler (gcc) installed?
> [root@n7bfs predict-2.2.1]#
> 
> 
> Now , what I get from that is that my node box does not have curses installed.
> 
> Hmm , so I check and sure enough it has "ncurses" installed , but not curses, 
> so I check all 3 install cd's and none have a curses package on them , so I 
> check the SuSE install dvd and sure enough -it- has it!

Most likely your system is lacking the ncurses development package.  To
keep installation size smaller the binary library and files needed for
compiling packages that use the binary library are in seperate packages.
So, just install ncurses-dev or something similar and you should be
fine.

73, de Nate >>

-- 
 Wireless | Amateur Radio Station N0NB          | "We have awakened a
 Internet | n0nb@networksplus.net               | sleeping giant and
 Location | Bremen, Kansas USA EM19ov           | have instilled in him
  Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
             http://www.qsl.net/n0nb/           | - Admiral Yamamoto

  parent reply	other threads:[~2002-12-16  2:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16  0:28 installing Predict on a RedHat 7.3 box , no go :^( Douglas Cole
2002-12-16  1:56 ` Douglas Cole
2002-12-16  2:02 ` Nate Bargmann [this message]
2002-12-16  4:03   ` Hisashi T Fujinaka
2002-12-16 17:24     ` John
2002-12-17  2:54       ` Douglas Cole
2002-12-16 10:26 ` Matti Aarnio

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=20021216020207.GJ448@localhost \
    --to=n0nb@networksplus.net \
    --cc=linux-hams@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.