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 01:23:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mo DeJong wrote:
> > This is because some apps need a pure cygwin/UNIX version of Tcl
> > to work correctly.  It was kind of pain to learn that since I'd
> > already done the upgrade in and found a dejagnu
> > and friends wouldn't work....
> What does that have to do with the win/ subdir and the VC++ build?

Not really sure.

> I was under the impression that the tcl/cygwin directory was where
> this "pure Cygwin" layer was going to live. I took a peek and
> it appears there is a file in there too, so why would you
> want to also create one in the ../unix directory? I think it is just plain
> wrong to create a ../unix/ file from the win subdirectory.
> For one thing, the @VAR@ variable names are not always the same.
> Also, it breaks the macros that load There must be some
> other way to solve the problem, it is just that I don't understand what
> the problem was.

Well, the apps being built think they are being built under UNIX
and look in the ../unix location.

A more correct solution would be to create a ../cygwin/
and make all the apps currently using the ../unix/
cygwin aware so they know to look in the ../cygwin directory.

The real down side of this is that you've got to make
at least expect (maybe dejagnu and some other Tcl dependent
binutils apps) cygwin aware.

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.


  reply	other threads:[~2002-02-21  8:08 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 [this message]
2002-02-21 11:00       ` Mo DeJong
2002-02-21 12:06         ` Ian Roxborough
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).