From: Dave Murphy <wintermute2k4@ntlworld.com>
To: afink@sarance.com
Cc: insight@sources.redhat.com
Subject: Re: Insight on Cygwin : GUI is not showing up
Date: Thu, 29 Sep 2005 19:08:00 -0000 [thread overview]
Message-ID: <433C3B9E.7060206@ntlworld.com> (raw)
In-Reply-To: <200509291835.j8TIZYoN006363@webmail3.megamailservers.com>
a.fink wrote:
>Hi
>
>I'm trying to build and run Insight-6.1 on Cygwin/X, on a Windows XP SP2 host.
>
>
>$> cp ~/insight-6.1.tar.gz /usr/src/archives
>$> cd /usr/src
>$> tar -xzvf ./archives/insight-6.1.tar.gz
>$> cp ~/cyg-tcl-sehfix.diff /usr/src/insight-6.1
>$> cd /usr/src/insight-6.1/tcl/win
>$> patch -p 2 < ../../cyg-tcl-sehfix.diff
>$> cd /usr/src/insight-6.1
>$> ./configure --target=mips-elf
>$> make
>$> make install
>
>
>
you need to add --enable-gdbtk when configuring, you should then get 3
binaries (assuming everything went well) insight (gui), gdb (cli)and
gdbtui(curses interface)
>I have had major failures with ddd, and now with Insight, and people around me
>are waiting for these tools.
>Here's a good example of OSS not being the good choice for anyone :/
>
>
Sometimes it just takes a little perseverance. I've recently managed to
successfully built insight 6.1 with gdb 6.3 patched in for native
windows host and arm-elf target using msys/mingw. The latest gdb from
CVS head now builds with this enviroment with minimal patching - still
having a bit of trouble convincing it to add Insight but I'll get there
in the end.
Dave
next prev parent reply other threads:[~2005-09-29 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 18:36 a.fink
2005-09-29 19:08 ` Dave Murphy [this message]
2005-09-29 22:17 ` Accounts
2005-09-30 15:21 ` Dave Murphy
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=433C3B9E.7060206@ntlworld.com \
--to=wintermute2k4@ntlworld.com \
--cc=afink@sarance.com \
--cc=insight@sources.redhat.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).