So this has been fixed (almost immediately after I opened the Trac ticket http://trac.clozure.com/ccl/ticket/1109!) in the trunk in:
http://trac.clozure.com/ccl/changeset/15892
Now I am wondering how often the binaries (e.g. wx86cl.exe) in http://svn.clozure.com/publicsvn/openmcl/trunk/windows/ccl get rebuilt? Is there a nightly build so that I can simply do an
svn update
on this, or is it time to get set up with gcc on Windows and perform the Windows build of the trunk myself, in order to test this?
Regards,
Dave
On Wed, Sep 4, 2013 at 4:36 PM, Dave Cooper david.cooper@genworks.comwrote:
So I'm trying to get the ASDF test suite running on Windows, and tracked this down as one of the failures for CCL (32-bit and 64-bit). (there were 5 failures out of 47 tests, I haven't looked at the rest yet).
This can be replicated as follows (with files from
https://www.dropbox.com/sh/jc2cqwpkp06dupm/7lgyRUdwZ5/cl/tests/simple ):
[below, substitute ".../'" for your actual path to the test files]:
(lisp-implementation-version)
"Version 1.9-r15765 (WindowsX8664)"
(compile-file ".../try1")
(compile-file ".../try2")
(ccl:fasl-concatenate ".../try.wx64fsl" (list ".../try1.wx64fsl"
".../try2.wx64fsl"))
(load ".../try.wx64fsl")
ERROR: Not a FASL file.
Does anyone recognize what might be going on?
-- My Best,
Dave Cooper, Genworks Support david.cooper@genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699