ASDF 3.1.5 test suite issues on ACL (8.2 and 10.0 GM)

[Kevin Layer]

Robert Goldman wrote:

>> On 9/14/15 Sep 14 -5:36 PM, Kevin Layer wrote:
>> > Faré wrote:
>> > 
>> >>>>>> @thor[git:master]$ ALLEGRO=/c/acl100/alisp make l=allegro test-lisp
>> >>>>>>> ALLEGRO=/c/acl100/alisp
>> >>>>>> I believe this should be ALLEGRO=c:\acl100\alisp ? (with proper shell escaping).
>> >>>>>> If using cygwin, $(cygpath ...) can help.
>> >>>>
>> >>>> The test scripts are written in BASH, so that would not be correct for
>> >>>> them.  ACL uses native Windows pathnames, but BASH doesn't.
>> >>>>
>> >>>> In any case, I tried it, and it didn't work.  I doubled the \'s, too.
>> >>>>
>> >>> In the minimakefile branch, the test scripts are written in Common
>> >>> Lisp, which if you use a native implementation (CCL is used by
>> >>> default), uses native Windows pathnames. Which is why I recommend
>> >>> using it, since that might simplify configuration somewhat.
>> >>>
>> >>>> I'm going to wait for you guys to get the Windows tests working before
>> >>>> I use them.  It is just too confusing for a non-ASDF devel like me.
>> >>>>
>> >>> Tests worked for me on Windows using Allegro 9.0 last weekend with
>> >>> 3.1.5.7 in the minimakefile branch.
>> >>> I have not tried Allegro 10.0 or Allegro but I believe they would work
>> >>> just as well.
>> > 
>> > Perhaps you can give me the exact command you used.  I couldn't find
>> > something that worked.
>> > 
>> 
>> I'll try this today on windows with the GM. Do you use cygwin?

Yes.  Windows without Cygwin is nearly impossible to use.

Btw, I haven't had time to try any of the suggestions, because I'm
been swamped.

Thanks for helping with this.

>> 
>> I am going to stick to master; I still don't understand minimakefile,
>> and I don't have time to learn its scripting language now.
>> 
>> I have to get to the office to get at my windows VM; I'll report back
>> after that.
>> 
>> Best,
>> r