Did you got submodules update --init or so to get the latest
lisp-invocation ?

On Tue, Feb 28, 2017, 13:57 Robert Goldman <rpgold...@sift.net> wrote:

> On Linux I get test failures for run-program as follows:
>
> allegro8_64 failed test-program.script
> allegro8_64_s failed test-program.script
> allegro_64 failed test-program.script
> allegro_64_s failed test-program.script
> allegromodern8_64 failed test-program.script
> allegromodern8_64_s failed test-program.script
> allegromodern_64 failed test-program.script
> allegromodern_64_s failed test-program.script
> ccl failed test-program.script
> clisp failed test-program.script
> cmucl failed test-program.script
> ecl failed test-program.script
> lispworks failed test-program.script
> mkcl failed test-program.script
> sbcl failed test-program.script
>
> These all seem to be due to test code passing :CONSOLE T to INVOKE-LISP
>
> Cheers,
> R
>
>

Reply via email to