From: Ian Roxborough <irox@redhat.com>
To: Mo DeJong <supermo@bayarea.net>
Cc: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: Fixing build bustage under VC++
Date: Wed, 20 Feb 2002 21:13:00 -0000 [thread overview]
Message-ID: <3C74865C.3F1EB59A@redhat.com> (raw)
In-Reply-To: <20020220175911.48e153f5.supermo@bayarea.net>
Mo DeJong wrote:
>
> Hi all.
>
> I took a quick look at why sourcenav fails to build under VC++ these days.
> The first problem I found showed up when Itcl tried to load tclConfig.sh and
> pulled it out of the tcl/unix subdirectory instead of tcl/win. After poking
> around for a bit, I found that the following change was to blame for this:
>
> 2001-09-12 Ian Roxborough <irox@redhat.com>
>
> * win/configure.in: Set DL_LIBS and MATH_LIBS. Create
> unix/tclConfig.sh.
>
> Index: configure.in
> ===================================================================
> RCS file: /cvs/src/src/tcl/win/configure.in,v
> retrieving revision 1.4
> retrieving revision 1.5
> diff -u -r1.4 -r1.5
> --- configure.in 2001/09/09 23:56:10 1.4
> +++ configure.in 2001/09/13 00:38:49 1.5
> @@ -230,5 +235,5 @@
> AC_SUBST(MAKE_DLL)
> AC_SUBST(MAKE_EXE)
>
> -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? The ChangeLog message seems to
> indicate that it has something to do with getting the build working with
> the Cygwin compiler. We can't really have two tclConfig.sh scripts like
> this because it breaks the m4 macro that searches for either unix/tclConfig.sh
> or win/tclConfig.sh.
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....
Ian.
next prev parent reply other threads:[~2002-02-21 4:17 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 [this message]
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
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=3C74865C.3F1EB59A@redhat.com \
--to=irox@redhat.com \
--cc=sourcenav@sources.redhat.com \
--cc=supermo@bayarea.net \
/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).