From: Anthony Green <green@moxielogic.com>
To: Bruno Haible <bruno@clisp.org>
Cc: libffi-discuss@sourceware.org
Subject: Re: Integrating bhaible's libffi testsuite
Date: Sun, 18 Mar 2018 02:50:00 -0000 [thread overview]
Message-ID: <CACxje599emL-=nVFxGs1oVT_Q3zt48v7yvp22_AQavDV7GpDCg@mail.gmail.com> (raw)
In-Reply-To: <2304423.D34OM0l70f@omega>
Bruno -- this is done now. Thanks!
AG
On Tue, Mar 13, 2018 at 9:49 AM, Bruno Haible <bruno@clisp.org> wrote:
> Hi Anthony,
>
>> After a few minor hacks, I've integrated Bruno's libffi testsuite into
>> our dejagnu framework, so each test is run individually, abort()'s on
>> failure, etc. It runs much more slowly but is suitable for automation
>> on embedded targets.
>
> You're welcome.
>
> Can it still be run "standalone" (i.e. without 'expect' and dejagnu)?
> I mean, on many machines I have access to, there is 'gcc' and 'make' installed
> but no 'tcl' and no 'expect'.
>
> Bruno
>
prev parent reply other threads:[~2018-03-18 2:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 13:31 Anthony Green
2018-03-13 13:50 ` Bruno Haible
2018-03-13 14:23 ` Anthony Green
2018-03-18 2:50 ` Anthony Green [this message]
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='CACxje599emL-=nVFxGs1oVT_Q3zt48v7yvp22_AQavDV7GpDCg@mail.gmail.com' \
--to=green@moxielogic.com \
--cc=bruno@clisp.org \
--cc=libffi-discuss@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).