Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: patch for expect to build on cygwin
Date: Mon, 14 Jul 2003 19:41:00 -0000	[thread overview]
Message-ID: <20030714194108.GB6543@redhat.com> (raw)
In-Reply-To: <orsmp89axf.fsf@free.redhat.lsd.ic.unicamp.br>

On Mon, Jul 14, 2003 at 04:15:56PM -0300, Alexandre Oliva wrote:
>I'm not sure this is the best place to post patches for expect, but we
>seem to have other s.r.c-local changes similar to this, and I
>understand we have expect only because it's used by dejagnu, and
>dejagnu is regarded as part of gdb in s.r.c, so I'm only posting it
>here.  The problem was that, on Cygwin, expect/configure couldn't find
>the tk config file in the build tree because it wouldn't search tk/win

Why is expect looking for tk at all?

cgf


  reply	other threads:[~2003-07-14 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 19:16 patch for expect to build on Cygwin Alexandre Oliva
2003-07-14 19:41 ` Christopher Faylor [this message]
2003-07-15  3:34   ` patch for expect to build on cygwin Alexandre Oliva
2003-07-15 18:37 ` patch for expect to build on Cygwin Alexandre Oliva

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=20030714194108.GB6543@redhat.com \
    --to=cgf@redhat.com \
    --cc=gdb-patches@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