I just re-tested this on Mac, Linux and Windows, and everything I tried
passed. So I think we are good to release. I'll have another look at
updating the Changelog.
If anyone out there knows the right tooling for doing that, I'd
appreciate a pointer! I have been using the ChangeLog mode for emacs,
and some settings seem to disagree with what the Debian format would
On 8 Apr 2018, at 11:05, Faré wrote:
I couldn't reproduce with AllegroExpress 10.1 on Linux amd64.
So I gave a closer look on the Windows VM, rm'ing all the files in
before I retried, and looked at the minimal logs for the issue.
The warnings were a false lead: Allegro does issue them, but they are
caught by the build system, so were not the issue.
The real issue was that allegro was looking for alisp.exe.dxl instead
I thus modified run-tests.sh so it will handle this case with more
All the tests then passed except test-multiple (which works for me on
Unsurprisingly, I see test-multiple uses ln -s and has an ugly
workaround on Windows
that doesn't work on sbcl, either. I moved it from using ln -s to
which modified the behavior in ways I admit I don't fully comprehend.
I documented the parts I did understand.
test-multiple exercises a really dark corner of the design, anyway,
one that we're trying to deprecate, badly-named secondary systems.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
You may easily play a joke on a man who likes to argue — agree with
— Edgar Waston Howe
On Sat, Apr 7, 2018 at 3:22 PM, Robert Goldman <rpgold...@sift.net>
Got the same issue:
Warning: FIRST-FEATURE is defined more than once as `operator' in
Warning: IMPLEMENTATION-TYPE is defined more than once as `operator'
Warning: *IMPLEMENTATION-TYPE* is defined more than once as
in file build\asdf.lisp.
Warning: OPERATING-SYSTEM is defined more than once as `operator' in
Warning: ARCHITECTURE is defined more than once as `operator' in file
I'll see if I can figure out what causes this. EVAL-WHEN is a likely
More as I have news,