Ok. Maybe we'll have to issue a 3.1.5 and then follow it almost immediately with a 3.1.6 that will have better Windows support. THEN we can finally move forward again. Best, R
Sent from my iPhone > On Jun 27, 2015, at 23:40, Faré <f...@tunes.org> wrote: > >> On Fri, Jun 26, 2015 at 4:49 PM, Robert Goldman <rpgold...@sift.net> wrote: >> Sorry -- I've been traveling, so sat on this bug report for a while. >> Here's a test failure from Windows ACL. Looks like ACL is somehow not >> running the windows CWD program helper (which should invoke CMD.EXE), >> but instead is just taking the command and treating it as its own output. > Indeed, %run-program has these lines: > ;; NB: We do NOT add cmd /c here. You might want to. > #+(or allegro clisp) command > > Retrospectively, that's probably a mistake. > >> which suggests we should modify %NORMALIZE-COMMAND for Allegro to >> prepend "CMD /C " to all commands when on windows. > Yup. > >> I'll test this myself the next time I get into the office, but that >> might not be till Monday afternoon. Or I might get lucky and find that >> I can remotely access my windows VM.... > I'll be back from camping this Sunday night. Hopefully next weekend I > have time to try. > > The situation is becoming pressing: the latest sbcl has made it to > debian testing, and is incompatible with the asdf 3.1.4 that is > currently available there. We really ought to issue a new asdf ASAP. > > —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org > Reality must take precedence over public relations, > for Mother Nature cannot be fooled. > — R.P. Feynman >
