From: Bruno Haible <bruno@clisp.org>
To: Anthony Green <green@moxielogic.com>
Cc: libffi-discuss@sourceware.org
Subject: Re: Integrating bhaible's libffi testsuite
Date: Tue, 13 Mar 2018 13:50:00 -0000 [thread overview]
Message-ID: <2304423.D34OM0l70f@omega> (raw)
In-Reply-To: <CACxje585b0qKd73NiqXU0H7on6CaTurp7Ew5W5wLKwE4wdqo7g@mail.gmail.com>
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
next prev parent reply other threads:[~2018-03-13 13: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 [this message]
2018-03-13 14:23 ` Anthony Green
2018-03-18 2:50 ` Anthony Green
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=2304423.D34OM0l70f@omega \
--to=bruno@clisp.org \
--cc=green@moxielogic.com \
--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).