From: Keith Seitz <keiths@cygnus.com>
To: Raymond Jou <raymondj@cognigine.com>
Cc: <insight@sources.redhat.com>
Subject: Re: FW: Insight Installation Bug
Date: Fri, 14 Sep 2001 10:23:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0109141015450.2096-100000@makita.cygnus.com> (raw)
In-Reply-To: <NFBBICKKNMHIJLOFJIMGCEEBCBAA.raymondj@cognigine.com>
On Fri, 14 Sep 2001, Raymond Jou wrote:
> I am encountering an installation bug that Insight looks for the Tcl library
> in
> $install_dir/libgui/library
> rather than in
> $install_dir/share/cygnus/gui
I've never seen this before...
> linux04:/home/raymondj/work/install/Linux>bin/gdb
> ide_initialize_paths failed: Can't find the GUI Tcl library in the following
> directories:
> /usr/share/cygnus/gui
> /share/cygnus/gui
> /home/raymondj/work/install/Linux/libgui/library
> /usr/share/cygnus/ide
> /share/cygnus/ide
> /home/raymondj/work/install/Linux/libide/library
>
>
> linux04:/home/raymondj/work/build/build_test/SW/tools/insight-5.0>head
> config.status
>
> #!/bin/sh
> # This file was generated automatically by configure. Do not edit.
> # This directory was configured as follows:
> ./configure --host=i686-pc-linux-gnu --target=osp192 --program-prefix=c --pr
> efix=/home/raymondj/work/install/Linux --norecursion
> #
May I recommend that you not build in the source directory? This may be a
total red herring, but I definitely do not recommend doing this.
Based on the configury that I see above, I would expect libgui to look in
/home/raymondj/work/install/Linux/share, but it doesn't... I don't know if
there was something wrong with the 5.0 release (could be, it was a really
random, bit-rotted "release" compared to what's available now).
Try searching the mailing list? I dunno what else to say...
> Our Insight/gdb code base was Insight-5.0 that we downloaded back in April
> of 2001. Thank you very much for your help.
Ok, not what most people want to hear, BUT... Have you tried a newer
version of insight? CVS is a little broken right now, but the 5.1 branch
is not too bad. If it works there, we would at least have something to
look at...
FWIW, here's how I build:
$ ls
src/
$ mkdir linux
$ cd linux
$ ../src/configure --prefix=/home/keiths/insight \
--exec-prefix=/home/keiths/insight/H-i686-pc-linux
$ make all-gdb install-gdb
See if doing this helps any. I'll see about getting the 5.0 "release" and
building it as you have.
Keith
next prev parent reply other threads:[~2001-09-14 10:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 10:10 Raymond Jou
2001-09-14 10:23 ` Keith Seitz [this message]
2001-09-14 10:52 ` Keith Seitz
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=Pine.GSO.4.33.0109141015450.2096-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=insight@sources.redhat.com \
--cc=raymondj@cognigine.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).