CentOS 6 compatibility

[dimitri]

Current version (as in Quicklisp latest release) of cl-fad is not usable in CentOS 6 with SBCL out of the box, because it's using the sb-ext:delete-directory function that appeared in SBCL 1.0.44.

I wonder how easy it is to add compatibility to that. If that's simple enough, then I think it's worth the trouble.

A user of my software (pgloader, which depends on cl-fad) reported some details:

[rjgonzale@cloud1 pgloader]$ cat /etc/redhat-release 
CentOS release 6.4 (Final)

from epel I installed

[rjgonzale@cloud1 pgloader]$ sbcl --version
SBCL 1.0.38-3.el6

And the error is...

[rjgonzale@cloud1 pgloader]$ ./pgloader.lisp --help
; Upgrading ASDF from version 2.010 to version 2.26
Loading quicklisp and the pgloader project and its dependencies...
;
; compilation aborted because of fatal error:
;   SB-INT:SIMPLE-READER-PACKAGE-ERROR at 13483 (line 282, column 30)
on
#<SB-SYS:FD-STREAM ;
for
"file /home/rjgonzale/quicklisp/dists/quicklisp/software/cl-fad-0.7.2/fad.lisp" ;
{10042479D1}>: ;     Symbol "DELETE-DIRECTORY" not found in the SB-EXT
package.

[hanshuebner]

You'll have to find out how to delete a directory with SBCL 1.0.38 and
supply a patch that conditionally uses that other way for versions of SBCL
before 1.0.44. A pull request would be welcome.

2013/9/20 Dimitri Fontaine [email protected]

Current version (as in Quicklisp latest release) of cl-fad is not usable
in CentOS 6 with SBCL out of the box, because it's using the
sb-ext:delete-directory function that appeared in SBCL 1.0.44.

I wonder how easy it is to add compatibility to that. If that's simple
enough, then I think it's worth the trouble.

A user of my software (pgloader, which depends on cl-fad) reported some
details:

[rjgonzale@cloud1 pgloader]$ cat /etc/redhat-release
CentOS release 6.4 (Final)

from epel I installed

[rjgonzale@cloud1 pgloader]$ sbcl --version
SBCL 1.0.38-3.el6

And the error is...

[rjgonzale@cloud1 pgloader]$ ./pgloader.lisp --help
; Upgrading ASDF from version 2.010 to version 2.26
Loading quicklisp and the pgloader project and its dependencies...
;
; compilation aborted because of fatal error:
; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 13483 (line 282, column 30)
on
#<SB-SYS:FD-STREAM ;
for
"file /home/rjgonzale/quicklisp/dists/quicklisp/software/cl-fad-0.7.2/fad.lisp" ;
{10042479D1}>: ; Symbol "DELETE-DIRECTORY" not found in the SB-EXT
package.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/9
.

[dimitri]

Thanks for willing to consider a compatibility patch here. I'll investigate how to fix the problem and get back with a patch, time permitting!

[amitlan]

Was this ever addressed (maybe elsewhere)?

[hanshuebner]

Not to my knowledge. I'd recommend using a version of SBCL that is less
ancient.

2015-01-21 11:25 GMT+01:00 Amit Langote [email protected]:

Was this ever addressed maybe elsewhere?

Reply to this email directly or view it on GitHub
#9 (comment).

[dimitri]

Yeah I managed to have a build machine with a recent enough SBCL, and to then only deploy the binary artefact given by buildapp, so that I don't have such a pressing need for a backward compatible solution in cl-fad.

Also, I have to admit that I now use uiop pathnames facilities rather than anything else, because of the way asdf and uiop are distributed and mainly already available (in modern enough versions of SBCL, again).

[Hellseher]

I've got the same issue when try to compile CL-FAD on CentOS 6

#: cat /etc/redhat-release 
CentOS release 6.7 (Final)
#: sbcl --version
SBCL 1.0.38-3.el6

Used Quicklisp to get CL-FAD

; Loading "cl-fad"
; compilation aborted because of fatal error:
;   SB-INT:SIMPLE-READER-PACKAGE-ERROR at 13483 (line 282, column 30) on
; #<SB-SYS:FD-STREAM
; for   "file /root/quicklisp/dists/quicklisp/software/cl-fad-.7.3/fad.lisp"
;    {1003A91E91}>:
;     Symbol "DELETE-DIRECTORY" not found in the SB-EXT package.

And struggling to compile new version on SBCL...

[stassats]

That SBCL version is even older now, even less incentive to support it.

[Hellseher]

Any clue how to compile last one using old SBCL 1.0.38? So far I've got error.

[dimitri]

Just upgrade your SBCL to something less ancient, really.