From: Mo DeJong <supermo@bayarea.net>
To: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: Fixing build bustage under VC++
Date: Thu, 21 Feb 2002 00:08:00 -0000 [thread overview]
Message-ID: <20020220231348.4c9bb314.supermo@bayarea.net> (raw)
In-Reply-To: <3C74865C.3F1EB59A@redhat.com>
On Wed, 20 Feb 2002 21:32:12 -0800
Ian Roxborough <irox@redhat.com> wrote:
...
> > -AC_OUTPUT(Makefile tclConfig.sh tcl.hpj)
> > +AC_OUTPUT(Makefile tclConfig.sh tcl.hpj ../unix/tclConfig.sh)
> >
> > My question is, why would the tcl/win configure script need to generate
> > a tclConfig.sh in the ../unix directory?
...
> 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 source.redhat.com and found a dejagnu
> and friends wouldn't work....
What does that have to do with the win/ subdir and the VC++ build?
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 tclConfig.sh.in 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/tclConfig.sh file from the win subdirectory.
For one thing, the @VAR@ variable names are not always the same.
Also, it breaks the macros that load tclConfig.sh. There must be some
other way to solve the problem, it is just that I don't understand what
the problem was.
Mo
next prev parent reply other threads:[~2002-02-21 7:14 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 [this message]
2002-02-21 1:23 ` Ian Roxborough
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:
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=20020220231348.4c9bb314.supermo@bayarea.net \
--to=supermo@bayarea.net \
--cc=sourcenav@sources.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).