Re: [asdf-devel] Possible problem with check-compile-results

2013-08-24 Thread Stelian Ionescu
On Fri, 2013-08-23 at 13:40 -0500, Robert Goldman wrote: > I would be grateful if someone could confirm this for me. > > I see this in quickloading BABEL on a relatively recent SBCL > 1.1.7.112.master.104-d62278d > > Babel crashes on compiling: > > caught ERROR: > ; (during macroexpansion of (

Re: [asdf-devel] Possible problem with check-compile-results

2013-08-24 Thread Faré
You'd have to post the stack trace for us to tell. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org On Sat, Aug 24, 2013 at 5:02 PM, Robert Goldman wrote: > Yes, the underlying problem was a version skew. But I was wondering if this > problem tickled a problem in

Re: [asdf-devel] Possible problem with check-compile-results

2013-08-23 Thread Faré
That sounds like a problem with Babel and/or a library it uses — and indeed reminds me of a previous bug in Alexandria — is your Alexandria up to date? It's using a symbol as a format string, which happens to work on some implementations at some (un)safety levels. —♯ƒ • François-René ÐVB Rideau •

[asdf-devel] Possible problem with check-compile-results

2013-08-23 Thread Robert Goldman
I would be grateful if someone could confirm this for me. I see this in quickloading BABEL on a relatively recent SBCL 1.1.7.112.master.104-d62278d Babel crashes on compiling: caught ERROR: ; (during macroexpansion of (DEFINE-UCS :UCS-2LE ...)) ; #:~A-CODE-POINT-COUNTER fell through ETYPECAS