On Wed, Jun 18, 2014 at 1:55 AM, Faré <fahree@gmail.com> wrote:
Can you upgrade your ASDF from 3.0.3.0.2 to 3.1.2?
Does 3.1.2 require a patch? If it does, then let's get it pushed
upstream into e.g. 3.1.2.5.


I dropped in ASDF 3.1.2 from the release tarball in the MKCL 1.1.9
source tree as a direct replacement of the currently bundled ASDF.
It compiled fine. The whole MKCL build completes and installs as usual.
The thus resulting ASDF 3.1.2 reports all tests are good when
'make test l=mkcl" is run, as well as with 'make test-upgrade l=mkcl'.

But when I come to try an upgrade from 3.1.2 to 3.1.2.4 syntax-control
branch I then get a crash.  Here is attached the transcript of what
is produced at the repl.

The error message basically says that 'build/asdf.lisp' cannot be found.
And in fact it is missing (it used to be produced properly by 3.0.3.0.X).
If I drop to a shell prompt and do make build/asdf.lisp and try the
same upgrade again then it completes properly. So is there something
broken now with the ASDF bundle 'concatenate' ops?

 
NB: please send a diff; I can review it, but Robert should commit and
push it — I'm out of this business (except for the branches I wrote
and would like to see merged — Robert, any news about them?)


Would do but I don't quite understand how to fix what I just reported here above.
 
PS: minor issue, but when I (quit), I get this annoying message:
> (quit)

;; MKCL shutdown: Thread refused to be interrupted: Sleeping thread:
#<thread "Imported thread pool filler daemon" active detached (27380)
0x7f1aa19d0700 0000000003286000>, in file threads.d at line 1076.
;; MKCL shutdown: Killing thread #<thread "Imported thread pool filler
daemon" active detached (27380) 0x7f1aa19d0700 0000000003286000>.

Thanks for the report. I bet you get this only once in a blue moon. It is just
a harmless annoyance. It also just reminds me that there is still some practical
reality of thread programming I have come to terms with.  It is the very low frequency
combined with clear randomness that bothers me. I just have get back to it
and silence this nagger for good...

Thanks again.