public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "blakjak" <blakjak@singnet.com.sg>
To: "Keith Seitz" <keiths@redhat.com>
Cc: <insight@sources.redhat.com>
Subject: RE: Compilation of 5.3 on cygwin under Win2000
Date: Thu, 19 Dec 2002 08:25:00 -0000	[thread overview]
Message-ID: <DIEOLFHFLFIKGHKJEDMPCECICDAA.blakjak@singnet.com.sg> (raw)
In-Reply-To: <Pine.LNX.4.44.0212190800170.1495-100000@valrhona.uglyboxes.com>

Keith,

Again thanks. I faced problems compiling under those instructions. 
BISON didn't work. I think the help I got here would resolve those 
issues though.

I am pretty new to this game of compiling my own stuff straight of the
web so I rely heavily on what I read. It seems that most of it is 
developed/tested under UNIX/UNIX equivalents. I understand this and use
Redhat LINUX myself but as most of my clients work in a MS environment
(at least the users) then I am forced to develop in that arena.

Now that I have a working version of TK/TCL/ITCL/BISON can I compile 
the latest source of Insight without invoking the new versions of 
TCL/TK/ITCL/BISON/etc.? Obviously I cannot use the main ./configure 
followed by make. What I would like to do is force make to use the 
already compiled versions of TCL/etc. Is this possible without making
major edits to the large make file created by configure?

I have really appreciated your advice with this. Thanks a lot.


Regards,
BlakJak :]

P.S. I am fairly competent at Win API programming but I am not sure 
how this relates to TK/TCL never used it before. I was always 
interested in developing a full C/C++ GUI for GDB. It seems it would
be a lot easier if the libGDB was up and running. Are you aware of
the state of that?


-----Original Message-----
From: Keith Seitz [mailto:keiths@redhat.com]
Sent: 20 December 2002 00:03
To: blakjak
Cc: insight@sources.redhat.com
Subject: RE: Compilation of 5.3 on cygwin under Win2000


On Thu, 19 Dec 2002, blakjak wrote:

> Do you believe that the problems with the latest versions of TCL 
> and TK will be resolved sometime?

No one has stepped up to the plate to look at this. Well, actually several 
have, but no one has ever been heard from again.. If cygwin users have no 
interest in helping to fix the problems, then neither do I. I do not use 
cygwin much any more. Maybe that will change and I will pursue the 
problem, but for now, I have very little motivation to do anything about 
it.

> Is it possible to add a comment to the Web pages to say which is 
> the latest version of Insight that is not broken for Windows?

You can use any version of insight. It's the version of Tcl, Tk, Itcl, etc 
that is "broken". There is a web page on the insight home page that talks 
about this already, and explains how to use newer versions of Insight with 
older versions of tcl et al.

Keith

  reply	other threads:[~2002-12-19 16:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-15  1:07 Compilation of 5.3 on Cygwin " blakjak
2002-12-15  6:54 ` Insight 5.3 runtime error blakjak
2002-12-15  6:55   ` blakjak
2002-12-15 10:31 ` Compilation of 5.3 on cygwin under Win2000 Christopher Faylor
2002-12-16  3:34   ` blakjak
2002-12-16  8:55     ` Christopher Faylor
2002-12-19  6:41       ` blakjak
2002-12-19  8:03         ` Keith Seitz
2002-12-19  8:25           ` blakjak [this message]
2002-12-19  8:51             ` Keith Seitz
     [not found] ` <redirect-4820052@silicondust.com>
2002-12-15 10:54   ` Jafa
2002-12-15 10:59     ` Christopher Faylor
     [not found]     ` <redirect-4820057@silicondust.com>
2002-12-15 11:07       ` Jafa
     [not found] <redirect-4820036@silicondust.com>
2002-12-15  9:28 ` Compilation of 5.3 on Cygwin " Nick Kelsey

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=DIEOLFHFLFIKGHKJEDMPCECICDAA.blakjak@singnet.com.sg \
    --to=blakjak@singnet.com.sg \
    --cc=insight@sources.redhat.com \
    --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).