public inbox for
 help / color / mirror / Atom feed
From: Ian Roxborough <>
To: Mo DeJong <>
Cc: sourcenav <>
Subject: Re: Fixing build bustage under VC++
Date: Thu, 21 Feb 2002 12:06:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mo DeJong wrote:
> > What are your feelings on VC++ vs gcc for building SN?
> >
> > I'm left with the distinct impression building gcc
> > would be easier, but then again, I'm just talk about
> > compiling, I've yet to get it to run.
> I think we should shoot for getting the VC++ build working again before
> working on further gcc support under Windows. The main point of a
> SN 5.1 release is to get the bug fixes and Tcl/Tk 8.3 upgrade out to
> folks. I don't think that switching the release compiler at the same time
> is such a good idea. Last I remember, the VC++ build was working
> and SN was running (but, that was many moons ago). I seem to
> remember that I had 90% of the packages compiling with mingw, but
> there were a couple (perhaps Tix, db, or grep) that were not yet ported.
> I know that at least Tcl, Tk, Incr Tcl,  and Incr Tk compiled with gcc.

Everything compiles with gcc just now.  There is like one
link error in hyper.exe because the tclstubs library is
missing from the link line.

The runtime problems seem to do with a Tcl_Preserve call
setting the interp pointer to NULL, but I've not tracked
down why.  I think I've seen similar problems with the
gcc compiled wish83, however some thing about Insight's Init
code let's it avoid this problem.


  reply	other threads:[~2002-02-21 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 20:17 Mo DeJong
2002-02-20 21:13 ` Ian Roxborough
2002-02-21  0:08   ` Mo DeJong
2002-02-21  1:23     ` Ian Roxborough
2002-02-21 11:00       ` Mo DeJong
2002-02-21 12:06         ` Ian Roxborough [this message]
2002-02-20 23:14 ` Ian Roxborough

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).