Brian Dessent wrote:
> Probably because you have a mutant configuration: a source tree with the
> insight dirs present, but insight disabled. That or you are also
> missing the in-tree tcltk. I think using the source package from setup
I'm certainly missing the in-tree tcltk, so that could be th
Samuel Sparks wrote:
> Anyway, thanks for the suggestion. I'll try downloading the gdb
> tarball, but I'd really like to understand what I am doing wrong here
> - this seems like it should be simple enough (just need to have the
> proper include path or header files).
Probably because you have a
Brian Dessent wrote:
> (Insight is an overlay on top of the gdb tree.) If you don't want to
> build insight (which is what --disable-gdbtk means) then you shouldn't
I'm not currently planning on using insight, but it would be nice to
have it available.
> have those directories in your source tr
Samuel Sparks wrote:
> /usr/src/gdb-6.8-2/libgui/src/tclwinprint.c:26:22: tkWinInt.h: No such
> file or directory
AFAIK libgui is a component of insight. So it looks like you've got a
full copy of the gdb+insight tree, as opposed to a plain gdb tree.
(Insight is an overlay on top of the gdb tre
Hello All,
I am trying to build a Cygwin hosted gdb executable to remotely debug
Linux applications on a powerpc target, but the build breaks in the
libgui directory. Does anyone have any _insight_ into the issue?
I've started with a clean Cygwin download, and added the following
packages to the
5 matches
Mail list logo