public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Cannot run from build directory
@ 2000-10-10 11:10 Syd Polk
  2000-10-10 11:26 ` Duane Ellis
  0 siblings, 1 reply; 6+ messages in thread
From: Syd Polk @ 2000-10-10 11:10 UTC (permalink / raw)
  To: insight

If I build insight from cvs, and try to run from the build directory:

cd <builddir>/gdb
./gdb hello

I get an alert that says the following:

"Could not find the Iwidgets libraries.
Got nameofexec:
<builddir>/gdb/gdb
Error(s) were:
can't find package Iwidgets 3.0
Could not find in-place
versions of the Iwidgets files...."

etc.

We are looking into this internally.

It runs fine from the install folder, but you cannot run the gdbtk portion 
of the test suite. We are also looking into that.




Syd Polk		spolk@redhat.com
Engineering Manager	+1 415 777 9810 x 241
Red Hat, Inc.



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Cannot run from build directory
  2000-10-10 11:10 Cannot run from build directory Syd Polk
@ 2000-10-10 11:26 ` Duane Ellis
  0 siblings, 0 replies; 6+ messages in thread
From: Duane Ellis @ 2000-10-10 11:26 UTC (permalink / raw)
  To: spolk; +Cc: insight

here's what is happening:

the tcl/tk code is trying to backtrack from the executable filename
(argv[0]) and discover all the shared files. (ie: blah.tcl).

Use:   "strace -o foobar ./gdb.exe"

and watch what it tries to do. What is a real pain runing GDB under a
debugger that does not pass "argv[0]" in a nice way.

In your case, you have not 'installed' GDB, the files in 'gdbtcl2' are
not inplace. Nore are all the other TCL files, nor the itcl files,
nor....  and the list goes on.

Also, the way these are stored "pre-install" vrs "post-install" are
very different.

You basically have to install the entire thing.... you have no choice.

It's *NOT* something you are going to easily be able to fix.

there are some shell variables, TCL_LIB... or something like that you
can use to point to a directory or two... but that does not solve the
"pre-install" layout -vrs- "post-install" layout of files.

-Duane, who has been there and done that.

http://www.franklin.com/ebookman (see what I've been doing)

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Cannot run from build directory
  2000-10-12  8:48     ` Jim Ingham
@ 2000-10-12  9:55       ` Fernando Nasser
  0 siblings, 0 replies; 6+ messages in thread
From: Fernando Nasser @ 2000-10-12  9:55 UTC (permalink / raw)
  To: Jim Ingham; +Cc: insight

Jim Ingham wrote:
> 
> Fernando,
> 
> Thanks for this AND all your other efforts on behalf of Insight!!!  I know
> pushing this issue forward is in great part your own initiative (and
> probably evenings too, though I hope not).  It is much appreciated!
> 

Insight is a very sexy debugger GUI.  It deserves some attention.

I would not be able to do anything alone.  I am getting lots of help.  I have been
bugging you and Keith a lot and I know that you guys have other responsibilities
in your respective companies.  You guys have also helped a lot with the list.
Thanks a lot!

Mo, have also helped a lot.  He has registered bugs, suggestions and helped people on the
list as well (despite all the work he has to do on Source Nav already). Syd is keeping our
version of Tcl/Tk and working a lot to move us to the latest version of things.  He also jumps in
for clarifications when these issues show up in the list.   Chris Faylor and
Tom Tromey have also helped with the list, among other things. Several folks from gdb land
have been helping tracking down bugs that are related to interactions between the GUI and
the core code. Not to mention the managers here at Red Hat who did all they could to allow
me to work on it.  I have bugged Karen, Chris and Eric a lot to get funding for Insight.
Thanks, thanks, thanks!

And there is more help coming now.  Other people from the net are becoming interested
and willing to help. There are already more people trying to help others in the list,
some people helping me track some bugs (I took the intermediate messages off the list to
minimize traffic) and people asking how they can contribute.  Thanks folks!

But we won't go far unless more people from the net jumps in. We will have to make working
in Insight easier for this to happen, but I guess this will come with continuous
maintenance.


P.S.: Yes, evenings too, unfortunately.  But I believe that is because of the backlog.
I hope it will soon get a little more bearable and as more people start to help with
fixing bugs, improvements and list help things will get back to normal.

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Cannot run from build directory
  2000-10-11 19:05   ` Fernando Nasser
@ 2000-10-12  8:48     ` Jim Ingham
  2000-10-12  9:55       ` Fernando Nasser
  0 siblings, 1 reply; 6+ messages in thread
From: Jim Ingham @ 2000-10-12  8:48 UTC (permalink / raw)
  To: Fernando Nasser; +Cc: insight

Fernando,

Thanks for this AND all your other efforts on behalf of Insight!!!  I know
pushing this issue forward is in great part your own initiative (and
probably evenings too, though I hope not).  It is much appreciated!

Jim

> Jim Ingham wrote:
>> 
>> Duane,
>> 
>>> 
>>> You basically have to install the entire thing.... you have no choice.
>>> 
>>> It's *NOT* something you are going to easily be able to fix.
>>> 
>>> there are some shell variables, TCL_LIB... or something like that you
>>> can use to point to a directory or two... but that does not solve the
>>> "pre-install" layout -vrs- "post-install" layout of files.
>>> 
>>> -Duane, who has been there and done that.
>>> 
>>> http://www.franklin.com/ebookman (see what I've been doing)
>> 
>> Nooo...
>> 
>> I worked really hard to make it so you can run Insight from the build
>> directory.  I also had to fix it a whole bunch of times pver the past couple
>> of years.  I am no longer in the business of doing this, and it seems it has
>> broken again.  Just keep bugging Syd et al, and I am sure they will fix it
>> sooner or later.  This really should work.
>> 
> 
> It works fine on Linux.  It is broken on Cygwin (probably one of those
> path-style
> conversions missing).
> 
> There was a bug (I fixed last night) that would cause trouble if your source
> tree
> had both itcl/iwidgets2.2.0 and itcl/iwidgets3.0.0 which was hurting Syd but
> apparently has nothing to do with the Windows case.
> 
> It is my list of things to fix.
> 

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Cannot run from build directory
  2000-10-11 18:18 ` Jim Ingham
@ 2000-10-11 19:05   ` Fernando Nasser
  2000-10-12  8:48     ` Jim Ingham
  0 siblings, 1 reply; 6+ messages in thread
From: Fernando Nasser @ 2000-10-11 19:05 UTC (permalink / raw)
  To: Jim Ingham; +Cc: insight

Jim Ingham wrote:
> 
> Duane,
> 
> >
> > You basically have to install the entire thing.... you have no choice.
> >
> > It's *NOT* something you are going to easily be able to fix.
> >
> > there are some shell variables, TCL_LIB... or something like that you
> > can use to point to a directory or two... but that does not solve the
> > "pre-install" layout -vrs- "post-install" layout of files.
> >
> > -Duane, who has been there and done that.
> >
> > http://www.franklin.com/ebookman (see what I've been doing)
> 
> Nooo...
> 
> I worked really hard to make it so you can run Insight from the build
> directory.  I also had to fix it a whole bunch of times pver the past couple
> of years.  I am no longer in the business of doing this, and it seems it has
> broken again.  Just keep bugging Syd et al, and I am sure they will fix it
> sooner or later.  This really should work.
> 

It works fine on Linux.  It is broken on Cygwin (probably one of those path-style
conversions missing).

There was a bug (I fixed last night) that would cause trouble if your source tree
had both itcl/iwidgets2.2.0 and itcl/iwidgets3.0.0 which was hurting Syd but 
apparently has nothing to do with the Windows case.

It is my list of things to fix. 


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Cannot run from build directory
       [not found] <971299064.12857.ezmlm@sources.redhat.com>
@ 2000-10-11 18:18 ` Jim Ingham
  2000-10-11 19:05   ` Fernando Nasser
  0 siblings, 1 reply; 6+ messages in thread
From: Jim Ingham @ 2000-10-11 18:18 UTC (permalink / raw)
  To: insight

Duane,

> 
> You basically have to install the entire thing.... you have no choice.
> 
> It's *NOT* something you are going to easily be able to fix.
> 
> there are some shell variables, TCL_LIB... or something like that you
> can use to point to a directory or two... but that does not solve the
> "pre-install" layout -vrs- "post-install" layout of files.
> 
> -Duane, who has been there and done that.
> 
> http://www.franklin.com/ebookman (see what I've been doing)

Nooo...  

I worked really hard to make it so you can run Insight from the build
directory.  I also had to fix it a whole bunch of times pver the past couple
of years.  I am no longer in the business of doing this, and it seems it has
broken again.  Just keep bugging Syd et al, and I am sure they will fix it
sooner or later.  This really should work.

Jim


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2000-10-12  9:55 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-10-10 11:10 Cannot run from build directory Syd Polk
2000-10-10 11:26 ` Duane Ellis
     [not found] <971299064.12857.ezmlm@sources.redhat.com>
2000-10-11 18:18 ` Jim Ingham
2000-10-11 19:05   ` Fernando Nasser
2000-10-12  8:48     ` Jim Ingham
2000-10-12  9:55       ` Fernando Nasser

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).