public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: ralphbel@us.ibm.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/96: insite fails to find iwidgets library
Date: Mon, 16 Jul 2001 16:43:00 -0000	[thread overview]
Message-ID: <20010716233503.22454.qmail@sourceware.cygnus.com> (raw)

>Number:         96
>Category:       insight
>Synopsis:       insite fails to find iwidgets library
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 16 16:43:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     ralphBellofatto
>Release:        5.0
>Organization:
>Environment:
redhat linux 7.1
>Description:
I installed Redhat linux 7.1 (install everything option) on an IBM intellistation and then attempted to install the insight tar on the system.  I issued the ./configure and the make and the make install command.  After repairing a problem with the make file where the function to create the target direrectories was broken (reported previously today) I attempted to run it.

running gdb reported and error that it could not find the iwidgets library.  

I checked in /usr/local/lib and could not find any libraries relating to widgets, so I think there is something  broken with the install.  

I suspect that the install did not completly install all there was to install for the special version of TCL required by gdb.

I am rather anxious to get this working on Redhat 7.1 as insight is one of the better GUI's for GDB.


Please advise.

Ralph Bellofatto
Advisor Software Engineer.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-07-16 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 16:43 ralphbel [this message]
2002-01-04 13:43 kseitz

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=20010716233503.22454.qmail@sourceware.cygnus.com \
    --to=ralphbel@us.ibm.com \
    --cc=insight-gnats@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).