Does not build in SBCL 1.1.6+ about log4cl

[7max]

Will be fixed tomorrow, not near my box right now

Zach Beane [email protected] wrote:

I'm using the latest SBCL from git, and when I build log4cl, I get this error:

; caught ERROR: ; READ error during COMPILE-FILE: Lock on package SB-C violated when interning HAIRY-ARG-PROCESSOR while in package LOG4CL-IMPL.

—
Reply to this email directly or view it on GitHub.

[7max]

Fixed now, let me know if you get any other problems

[Ragnaroek]

Same error on SCBL 1.1.5, MacOS 10.8.
Will this be fixed in SCBL 1.1.7?

[sweagraff]

Same error on SBCL 1.1.7 on Linux

[7max]

@Ragnaroek @sweagraff This should have been fixed, but may have not been pulled into quicklisp yet

What does the output of

(asdf:component-version (asdf:find-system :log4cl)) 

say?

If its 1.0.0 or 1.0.1 then we have a problem and fix did not work, but if its 0.9.x then you need to pull "stable" branch until new QuickLisp is released.

[sweagraff]

I pulled the latest release and tried both master and stable. This is outside of quicklisp (using the lib directly).

For now I've moved back to an earlier release of sbcl.

Thanks.

Steve.

Sent from my iPhone

On May 4, 2013, at 7:54 AM, Max Mikhanosha [email protected] wrote:

@Ragnaroek @sweagraff This should have been fixed, but may have not been pulled into quicklisp yet

(asdf:component-version (asdf:find-system :log4cl))
say?

If its 1.0.0 or 1.0.1 then we have a problem and fix did not work, but if its 0.9.x then you need to pull "stable" branch until new QuickLisp is released.

—
Reply to this email directly or view it on GitHub.

[7max]

I just tried stable branch, with tip of SBCL and the fix is working here. It seems that on your machine, it tries to compile older source still. There is no reference to SB-C:HAIRY-ARG-PROCESSOR in the naming-sbcl.lisp anymore, other then in a a string used for FIND-SYMOBL.

The specific fix is in commit 3881f74

Your problem could be different, but I had been bitten by the following scenario many times before, when I include entire directory tree via ASDF:INITIALIZE-SOURCE-REGISTRY, or by using QL:LOCAL-PROJECT-DIRECTORIES to the a directory where all my Lisp stuff is located.

Then I would either clone or copy some project inside, such as git clone log4cl log4cl.bak but then ASDF and QL randomly find the .asd file in either old or new directory.. When cloning or moving different branches of a system, you need to be careful to make sure that ASDF can only find 1 .ASD file at a time.

[sweagraff]

Thanks. I'll check my sources and try again.

Steve

Sent from my iPhone

On May 4, 2013, at 1:23 PM, Max Mikhanosha [email protected] wrote:

I just tried stable branch, with tip of SBCL and the fix is working here. It seems that on your machine, it tries to compile older source still. There is no reference to SB-C:HAIRY-ARG-PROCESSOR in the naming-sbcl.lisp anymore, other then in a a string used for FIND-SYMOBL.

The specific fix is in commit 3881f74

Your problem could be different, but I had been bitten by the following scenario many times before, when I include entire directory tree via ASDF:INITIALIZE-SOURCE-REGISTRY, or by using QL:LOCAL-PROJECT-DIRECTORIES to the a directory where all my Lisp stuff is located.

Then I would either clone or copy some project inside, such as git clone log4cl log4cl.bak but then ASDF and QL randomly find the .asd file in either old or new directory.. When cloning or moving different branches of a system, you need to be careful to make sure that ASDF can only find 1 .ASD file at a time.

—
Reply to this email directly or view it on GitHub.

[sweagraff]

Thanks very much. That was it.

Steve

On May 4, 2013, at 1:23 PM, Max Mikhanosha [email protected] wrote:

I just tried stable branch, with tip of SBCL and the fix is working here. It seems that on your machine, it tries to compile older source still. There is no reference to SB-C:HAIRY-ARG-PROCESSOR in the naming-sbcl.lisp anymore, other then in a a string used for FIND-SYMOBL.

The specific fix is in commit 3881f74

Your problem could be different, but I had been bitten by the following scenario many times before, when I include entire directory tree via ASDF:INITIALIZE-SOURCE-REGISTRY, or by using QL:LOCAL-PROJECT-DIRECTORIES to the a directory where all my Lisp stuff is located.

Then I would either clone or copy some project inside, such as git clone log4cl log4cl.bak but then ASDF and QL randomly find the .asd file in either old or new directory.. When cloning or moving different branches of a system, you need to be careful to make sure that ASDF can only find 1 .ASD file at a time.

—
Reply to this email directly or view it on GitHub.