* Integrating bhaible's libffi testsuite
@ 2018-03-13 13:31 Anthony Green
2018-03-13 13:50 ` Bruno Haible
0 siblings, 1 reply; 4+ messages in thread
From: Anthony Green @ 2018-03-13 13:31 UTC (permalink / raw)
To: libffi-discuss, Bruno Haible
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.
Thank you, Bruno!
AG
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Integrating bhaible's libffi testsuite
2018-03-13 13:31 Integrating bhaible's libffi testsuite Anthony Green
@ 2018-03-13 13:50 ` Bruno Haible
2018-03-13 14:23 ` Anthony Green
2018-03-18 2:50 ` Anthony Green
0 siblings, 2 replies; 4+ messages in thread
From: Bruno Haible @ 2018-03-13 13:50 UTC (permalink / raw)
To: Anthony Green; +Cc: libffi-discuss
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Integrating bhaible's libffi testsuite
2018-03-13 13:50 ` Bruno Haible
@ 2018-03-13 14:23 ` Anthony Green
2018-03-18 2:50 ` Anthony Green
1 sibling, 0 replies; 4+ messages in thread
From: Anthony Green @ 2018-03-13 14:23 UTC (permalink / raw)
To: Bruno Haible; +Cc: libffi-discuss
Hi Bruno,
Now that I've made the changes, I can see how to modify them to make your
testsuite also behave as before. I'll try to do this today or tomorrow.
Thanks,
AG
On Mar 13, 2018 9:50 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
>
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Integrating bhaible's libffi testsuite
2018-03-13 13:50 ` Bruno Haible
2018-03-13 14:23 ` Anthony Green
@ 2018-03-18 2:50 ` Anthony Green
1 sibling, 0 replies; 4+ messages in thread
From: Anthony Green @ 2018-03-18 2:50 UTC (permalink / raw)
To: Bruno Haible; +Cc: libffi-discuss
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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-03-18 2:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-13 13:31 Integrating bhaible's libffi testsuite Anthony Green
2018-03-13 13:50 ` Bruno Haible
2018-03-13 14:23 ` Anthony Green
2018-03-18 2:50 ` Anthony Green
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).