On Mon, Sep 14, 2015 at 6:36 PM, Kevin Layer <layer@franz.com> wrote:
> Perhaps you can give me the exact command you used.  I couldn't find
> something that worked.
>
Attached are the relevant parts of an environment file that I sourced
into my cygwin bash shell with
. windows-env.sh

I tested it to work with both the master branch and the minimakefile
branch of ASDF,
with both Allegro 9.0 and 10.0.

You obviously have to adapt the various paths to your installation.

If you use the master branch:

make l=allegro test-lisp


If you use the minimakefile branch,
I recommend you install, configure and use CCL to drive the ASDF tests;
but as explained in the README.md, you can now export LISP=allegro
at which point the script asdf-tools.bat will try to use Allegro instead of CCL
(I just debugged that for you on Windows and Linux):

make l=allegro test-scripts

However, whereas using LISP=ccl as the driver correctly invokes buildi.exe,
using LISP=allegro as the driver leads to alisp.exe being called,
which is not what I wanted.
I haven't investigated why.

Note that at some point while I was tinkering with test configuration,
allegro was complaining about an incompatibility between fasl format
63 vs 66 while running test-program.script, which suggested either a
discrepancy between buildi and alisp, or more simply my failing to
cleanly separate allegro 9 from allegro 10.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Meta is Better. Anything you can do, I can do Meta. — Patrick Logan