public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Andreas.Karlsson@combitechsystems.com
Cc: ecos-discuss@sourceware.cygnus.com, insight@sourceware.cygnus.com
Subject: Re: Problem when configuring Insight on Linux
Date: Thu, 09 Nov 2000 06:08:00 -0000	[thread overview]
Message-ID: <3A0AAFD7.2A5C33EB@cygnus.com> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B0229AAB0@pluto.combitech.se>

Andreas.Karlsson@combitechsystems.com wrote:
> 
> Hi,
> 
> I installed Red Hat 6.2 and then exactly followed the instructions on eCos
> homepage but when configuring Insight-5.0 the following error occurs. I have
> been searching both eCos archive and Insights, there are more people having
> the same problem on both mailing lists but there are no solution:(
> 
> Any ideas?
> 

Something went wrong during your OS installation and you end up with no
terminal library installed.  You can fix this by installing the 
Package Group related to terminal support, if there is one, or some of
the individual RPMs for the things below.



> checking for cygwin... no
> 
> checking for tgetent in -lncurses... (cached) no
> 
> checking for tgetent in -lHcurses... no
> 
> checking for tgetent in -ltermlib... no
> 
> checking for tgetent in -ltermcap... (cached) no
> 
> checking for tgetent in -lcurses... (cached) no
> 
> checking for tgetent in -lterminfo... no
> 
> configure: error: Could not find a term library
> 
> Configure in /tmp/build/gdb/gdb failed, exiting.
> 
> /Andreas

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

      reply	other threads:[~2000-11-09  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09  1:43 Andreas.Karlsson
2000-11-09  6:08 ` Fernando Nasser [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=3A0AAFD7.2A5C33EB@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=Andreas.Karlsson@combitechsystems.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=insight@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).