From: "Brandon Metcalf" <bmetcalf@nortelnetworks.com>
To: Keith Seitz <kseitz@multitude.com>,
"Brandon Metcalf" <bmetcalf@nortelnetworks.com>
Cc: insight@sourceware.cygnus.com
Subject: Re: ide_initialize_paths failed: Can't find the GUI Tcl
Date: Tue, 04 Jan 2000 09:24:00 -0000 [thread overview]
Message-ID: <3.0.1.32.20000104092405.00a8fbe0@ZSC4C006.corpwest.baynetworks.com> (raw)
In-Reply-To: <3862525C.86A66F00@multitude.com>
At 08:48 AM 12/23/99 -0800, Keith Seitz wrote:
>Is the environment variable CYGNUS_GUI_LIBRARY set? If it is and it is
>pointing to la-la land, I guess that could cause problems.
>(Alternatively, you could attempt to set this variable to the location
>of this directory and see what happens...)
Hi Keith,
Setting CYGNUS_GUI_LIBRARY did the trick. The problem is that my install
directory structure looks like this:
root@lovett 0010-19991213 # ls -l
total 8
drwxr-xr-x 2 root root 512 Dec 22 10:06 AIX/
drwxr-xr-x 2 root root 512 Dec 22 10:06 HP-UX/
drwxr-xr-x 4 root root 512 Jan 4 09:13 SunOS/
drwxr-xr-x 6 root root 512 Dec 22 10:38 common/
where common contains architecture independent files such as the
share/cygnus/gui directory. Even though I specified this during the
configure phase, gdb can't find what it needs. After looking at the code,
I found that if I create the following symlink
root@lovett 0010-19991213 # ls -l SunOS
total 6
drwxr-xr-x 2 root root 512 Jan 4 09:14 bin/
drwxr-xr-x 2 root root 512 Dec 22 13:55 lib/
lrwxrwxrwx 1 root root 15 Jan 4 09:13 share ->
../common/share/
everything works fine without setting CYGNUS_GUI_LIBRARY. It seems like
this is a bug in the software because configure should take care of letting
gdb know where to find its dependencies.
Anyway, thanks for the tip.
Brandon
prev parent reply other threads:[~2000-01-04 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-22 10:59 Brandon Metcalf
1999-12-23 8:49 ` Keith Seitz
2000-01-04 9:24 ` Brandon Metcalf [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=3.0.1.32.20000104092405.00a8fbe0@ZSC4C006.corpwest.baynetworks.com \
--to=bmetcalf@nortelnetworks.com \
--cc=insight@sourceware.cygnus.com \
--cc=kseitz@multitude.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).