From: Alexandre Oliva <aoliva@redhat.com>
To: Christopher Faylor <cgf@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: patch for expect to build on cygwin
Date: Tue, 15 Jul 2003 03:34:00 -0000 [thread overview]
Message-ID: <oroezw5upt.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20030714194108.GB6543@redhat.com>
On Jul 14, 2003, Christopher Faylor <cgf@redhat.com> wrote:
> On Mon, Jul 14, 2003 at 04:15:56PM -0300, Alexandre Oliva wrote:
>> 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?
Don't, erhm, expect me to know the answer :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2003-07-15 3:34 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 ` patch for expect to build on cygwin Christopher Faylor
2003-07-15 3:34 ` Alexandre Oliva [this message]
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=oroezw5upt.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=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