public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Hugh Sparks <hugh@csparks.com>
To: insight@sourceware.org
Subject: Re: Steps to build Insight for Windows
Date: Thu, 10 Jan 2013 20:46:00 -0000	[thread overview]
Message-ID: <50EF2892.5040800@csparks.com> (raw)
In-Reply-To: <1357848662.20894.ezmlm@sourceware.org>

Thanks Roland Schwingel for the detailed instructions!
I was able to build and run Insight for mingw.

There is, however, a problem: When I load a program into the debugger 
(compiled with -O0 -g), I can only see assembly language. The window 
simply "blinks" when I try to select source mode. When I try to run the 
program, I get the message:

"Can not parse XML target description; XML support was disabled at 
compile time"

I noticed when following the instructions the list of required 
directories included 'expat'. But there was no expat directory in the 
archive I downloaded. The CVS was not working so I tried both of these 
with similar results:

      insight-6.8-1a.tar.bz2
      insight-weekly-7.0.50-20091130.tar.bz2

The CVS browser does work and I could see an expat directory. Evidently 
the archives I tried are too old? Is there somewhere I can download the 
appropriate sources? Any insight into why source code doesn't
appear in the debugger would be appreciated.

Thanks

-Hugh Sparks


       reply	other threads:[~2013-01-10 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1357848662.20894.ezmlm@sourceware.org>
2013-01-10 20:46 ` Hugh Sparks [this message]
2013-01-10 22:47   ` Keith Seitz
2012-11-02 10:06 Roland Schwingel
  -- strict thread matches above, loose matches on Subject: below --
2012-11-01  6:29 Kobus Engelbrecht

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=50EF2892.5040800@csparks.com \
    --to=hugh@csparks.com \
    --cc=insight@sourceware.org \
    /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).