From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <drow@false.org>, <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFC] Improve testsuite for poor expect behavior
Date: Thu, 18 Jun 2009 15:57:00 -0000 [thread overview]
Message-ID: <001201c9f02d$3ab7d310$b0277930$@u-strasbg.fr> (raw)
In-Reply-To: <E1MHIfx-0006b0-3H@fencepost.gnu.org>
> I will need to know the minimal set of Cygwin packages to install, for
> this to work.
To use cygwin expect with DJGPP gdb and the djgpp.exp
board file I sent, you will need a minimal installation plus
the dejagnu package (that should trigger the installation of
some other required packages).
Other packages that might be needed are:
- Bash (but it's probably part of base)
...
I have no other idea now, but that doesn't mean
that you will not need more...
One more thing that I forgot to tell you:
I had to manually force two things in djbuild/gdb/testsuite/site.exp
set objdir ./.
set TOOL_EXECUTABLE ../gdb.exe
The objdir is there to avoid translation from relative to absolute
pathes, which leads to conflits both for mingw32 and djgpp
as cygwin uses its own root dir and the /cygdrive/X for windows X:\ drive.
The TOOL_EXECUTABLE is needed because otherwise, as
I use the --host_board=djgpp which makes expect believe that
host is remote, it doesn't find the correct executable...
Part of expect is still incomprehensible for me ...
Pierre
next prev parent reply other threads:[~2009-06-18 15:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 23:00 Pierre Muller
2009-06-13 14:52 ` Doug Evans
2009-06-13 15:05 ` Daniel Jacobowitz
2009-06-13 20:29 ` Pierre Muller
2009-06-13 23:55 ` 'Daniel Jacobowitz'
2009-06-14 0:25 ` Joel Brobecker
2009-06-15 7:23 ` Pierre Muller
2009-06-16 14:58 ` Joel Brobecker
2009-06-16 23:29 ` Pierre Muller
2009-06-17 13:36 ` 'Daniel Jacobowitz'
2009-06-17 14:54 ` Joel Brobecker
2009-06-17 17:25 ` Eli Zaretskii
2009-06-17 19:39 ` Joel Brobecker
2009-06-18 14:38 ` Eli Zaretskii
2009-06-18 14:59 ` Joel Brobecker
2009-06-18 15:25 ` Eli Zaretskii
2009-06-18 15:33 ` Joel Brobecker
2009-06-18 15:58 ` Samuel Bronson
2009-06-18 23:02 ` Eli Zaretskii
2009-06-17 17:17 ` Eli Zaretskii
2009-06-17 20:17 ` Pierre Muller
2009-06-17 21:00 ` Pierre Muller
2009-06-18 14:33 ` Eli Zaretskii
2009-06-18 15:57 ` Pierre Muller [this message]
2009-06-18 16:08 ` Pedro Alves
2009-06-18 23:18 ` Eli Zaretskii
2009-06-18 16:19 ` Pedro Alves
2009-06-17 21:56 ` Pierre Muller
2009-06-18 14:48 ` Eli Zaretskii
2009-06-17 22:39 ` Pierre Muller
2009-06-17 22:43 ` 'Daniel Jacobowitz'
2009-06-17 22:54 ` Pierre Muller
2009-06-17 23:21 ` 'Daniel Jacobowitz'
2009-06-17 23:18 ` Joel Brobecker
2009-06-18 6:31 ` Mark Kettenis
2009-06-23 18:14 ` Joel Brobecker
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='001201c9f02d$3ab7d310$b0277930$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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