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

On Thu, 9 May 2002 12:36:55 -0700 (PDT)
Keith Seitz <keiths@redhat.com> wrote:

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

Is there some other list that this patch should be submitted to?

> 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.
> :-(

That -e flag is kind of interesting because it was to work around a bug in gcc. When both a WinMain() and a main() are found gcc incorrectly picks main() as the entry point even though -mwindows is passed. If this problem no longer exists in Cygwin gcc then the -e could be removed. I know it is required to build with Mingw 2.95.2, but I don't know about later releases. If this problem does exist, it manifests itself as a wish.exe that pops up the . window but no console.

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

It should break down when building Itcl under Windows. I have no idea why you would not run into this problem aside from something obvious like using an older config.cache that had tcl/win/tclConfig.sh cached. You might try looking at the output of configure when the Itcl configure is being run to see if it detects the config file in tcl/unix or tcl/win.

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

As far as I can tell, it was to avoid an error configuring expect. The expect patch fixes that problem so I can't see any reason not to apply the patch.

Mo

  reply	other threads:[~2002-05-09 21:15 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
2002-05-09 14:15   ` Mo DeJong [this message]
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=20020509142009.499f1d81.supermo@bayarea.net \
    --to=supermo@bayarea.net \
    --cc=insight@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).