public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Mo DeJong <supermo@bayarea.net>
Cc: <insight@sources.redhat.com>
Subject: Re: [Patch] Fixup tcl and expect build under Cygwin
Date: Thu, 09 May 2002 12:36:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.33.0205091232250.28406-100000@makita.cygnus.com> (raw)
In-Reply-To: <20020504195539.38533e30.supermo@bayarea.net>

Sorry for the delay...

On Sat, 4 May 2002, Mo DeJong wrote:

> 2002-05-04  Mo DeJong  <supermo@bayarea.net>
>
> 	* aclocal.m4 (CY_AC_PATH_TCLCONFIG, CY_AC_PATH_TKCONFIG,
> 	CY_AC_PATH_ITCLH): Update macros that search for tclConfig.sh
> 	and tkConfig.sh so that they also check the win/ subdirectory.
> 	Update macro that checks for itcl.h so that it looks in
> 	itcl/itcl/generic instead of itcl/src. These updates
> 	are needed to get things building correctly under Cygwin
> 	gcc and Tcl/Tk 8.3.
>  	* configure: Regen.

I cannot approve this (not really sure who can), but I remember doing
something similar in a sandbox to fix all the tcl/tk problems on cygwin.
There are several problems with our tcl/tk builds now;
tcl/generic/tclIntDecls.h has bugs, cygtcl.m4 wants to link with
"-e_WinMain@16", which is wrong, and a bunch more that I haven't found.
:-(

I'm trying to package these all up and check them in, but I keep getting
side-tracked. (You worked for Red Hat: you know how that goes.)

> 2002-05-04  Mo DeJong  <supermo@bayarea.net>
>
> 	* unix/tclUnixFCmd.c (DoCopyFile): Don't use mkfifo
> 	when compiling with Cygwin, since it is not supported.
>  	* win/configure: Regen.
> 	* win/configure.in: Don't emit ../unix/tclConfig.sh.
> 	This hack was breaking the snavigator build and was
> 	only needed because the expect build process was
> 	out of date.

Otherwise, as far as I can approve the tcl changes, I've only one
question... Why can I build with cygwin without build problems? (Ok,
expect doesn't build, but tcl/tk were "fine".)

I'll definitely approve the unix/tclConfig.sh thing, though. I never
understood why that was done.

Keith



  reply	other threads:[~2002-05-09 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 19:51 Mo DeJong
2002-05-09 12:36 ` Keith Seitz [this message]
2002-05-09 14:15   ` Mo DeJong
2002-05-09 14:21     ` Keith Seitz

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=Pine.GSO.4.33.0205091232250.28406-100000@makita.cygnus.com \
    --to=keiths@redhat.com \
    --cc=insight@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).