[Asdf-devel] clisp on Linux [was Re: ASDF Release?]

[Faré]

On Mon, Oct 6, 2014 at 5:12 PM, Robert P. Goldman <rpgoldman at sift.info> wrote:
> Faré wrote:
>
>> I get an all pass on Linux with my hand-compiled clisp.
>
> I have the clisp that you get with Linux Mint, and for me I get this
> failure:
>
> TEST ABORTED:
> These two expressions fail comparison with EQUAL:
>  (NEST
>  (LISP-INVOCATION:INVOKE-LISP :CROSS-COMPILE NIL :IMAGE-PATH
>   (NATIVE-NAMESTRING IMG) :EVAL
>   "(uiop:restore-image :entry-point 'hello:entry-point :lisp-interaction
> nil)"
>   :RUN-PROGRAM-ARGS '(:OUTPUT :LINES :ERROR-OUTPUT T))) evaluates to
> ("[4]> hello, world")
>  '("hello, world") evaluates to ("hello, world")
>
> This is the same failure I was getting on Mac OS X (and not the same one
> Dave was getting).
>
> clisp 2.49
>
> As a quick follow-up, when I start clisp the prompt looks like this for me:
>
> [1]>
>
> I am wondering if somehow your hand-built system gets a different prompt
> or somehow my prompts bleed through into program output in a way yours
> don't....
>
I don't understand how this error comes to be. I tried with the
ubuntu-provided clisp 2.49 (1:2.49-9ubuntu1) instead of the one I
custom-built from HEAD a few weeks ago, and it works fine, too. And so
I can't debug a problem I can't reproduce and can't fathom.

Can you identify what command is being run? e.g. by tracing
run-program in test-program.script. How does the dumped clisp
executable image behave without any of the provided arguments? Is
there some hidden configuration file that is biting us? Are we failing
to disable configuration files when calling the image?

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
If a nation values anything more than freedom, it will lose its freedom; and
the irony of it is that if it is comfort or money that it values more,
it will lose that, too.  — Somerset Maugham (1874–1965)