public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Clemens Valens <cvalens@yahoo.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Build failure on MinGW
Date: Fri, 12 Nov 2010 13:46:00 -0000	[thread overview]
Message-ID: <649639.95296.qm@web110202.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4CDCB26C.1040705@redhat.com>


> Here is finally some good news... I have just
> built/installed/run insight -- using ONLY
> sourceware-supplied sources (i.e., no ActiveState Tcl
> necessary) on mingw w/msys!
> 
> There are a few little problems, and I hope to have patches
> for those committed in the next day or two. Mind you, I also
> haven't tested it exhaustively -- just stepped through gdb
> with register, console, locals, stack, breakpoints windows
> open. Just a sanity check.
> 
> Keith
> 
> PS. Do you want to pursue your current course w/ActiveState
> tcl? If so, I'll need to see the configure/build logs...
> 

Hi Keith,

first of all, thank you very much for the effort you are putting in this! Maybe you should buy your wife an i-Pad, then you can keep her Windows machine.

To be honest I would prefer a solution with only sourceware-supplied sources. I think it would be better not to have to rely on (a lot of) external components, it is allready complicated enough the way it is now. But that's just my humble opinion. The ActiveState Tcl solution is probably very nice & useful for lots of people.

P.S. If I manage to build a working Windows executable, would I be allowed to put it up for downloading? (for free of course)

Clemens



      

      reply	other threads:[~2010-11-12 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1289408071.23303.ezmlm@sourceware.org>
2010-11-10 17:07 ` Clemens Valens
2010-11-10 19:18   ` Keith Seitz
2010-11-11 18:15     ` Clemens Valens
2010-11-11 22:21       ` Clemens Valens
2010-11-12  3:23         ` Keith Seitz
2010-11-12 13:46           ` Clemens Valens [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=649639.95296.qm@web110202.mail.gq1.yahoo.com \
    --to=cvalens@yahoo.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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).