Quicklisp in MCL (was Re: RMCL 6.0 with ASDF)
Chris Hanson <[email protected]> Fri, 1 Sep 2017 16:55:50 -0700
| Newsgroups | gmane.lisp.mcl.general |
|---|---|
| Message-ID | <[email protected]> |
--===============8725354823510240881== Content-Type: multipart/alternative; boundary="Apple-Mail=_AABB7D52-A1EE-4381-81BE-45DE08A72006" --Apple-Mail=_AABB7D52-A1EE-4381-81BE-45DE08A72006 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On Aug 29, 2017, at 1:58 AM, Chun Tian (binghe) <[email protected]> = wrote: >=20 > I don't see any hope to use Quicklisp directly in MCL, Why not? It seems feasible to get the latest ASDF working again, since = your RMCL 6.0 has a working ASDF to start from. I did some hacking to try to get the Quicklisp bootstrap working in MCL = 5.1 and only ran into one real issue, where minitar was extracting files = with slashes in the name instead of directories: = https://github.com/quicklisp/quicklisp-bootstrap/issues/17 = <https://github.com/quicklisp/quicklisp-bootstrap/issues/17>=20 I got the bootstrap working mainly by using #+mcl and #-mcl to = conditionalize the CCL support, and I think there was one thing I had to = tweak in 5.1 in the defpackage call because MCL didn=E2=80=99t support = one option. I had to do a little more in MCL 3.4, since there were a couple of = issues with using its binary TCP binary stream but those should probably = be patches to MCL 3.4 since they just seemed like implementation bugs=E2=80= =A6 Of course, I need to figure out how to make and use MCL patches, but = how hard could that be? :) -- Chris --Apple-Mail=_AABB7D52-A1EE-4381-81BE-45DE08A72006 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On = Aug 29, 2017, at 1:58 AM, Chun Tian (binghe) <<a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>> wrote:<br = class=3D""><div><blockquote type=3D"cite" class=3D""><br = class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" = class=3D""><div class=3D"">I don't see any hope to use Quicklisp = directly in MCL,</div></div></div></blockquote><br = class=3D""></div><div>Why not? It seems feasible to get the latest ASDF = working again, since your RMCL 6.0 has a working ASDF to start = from.</div><div><br class=3D""></div><div>I did some hacking to try to = get the Quicklisp bootstrap working in MCL 5.1 and only ran into one = real issue, where minitar was extracting files with slashes in the name = instead of directories: <a = href=3D"https://github.com/quicklisp/quicklisp-bootstrap/issues/17" = class=3D"">https://github.com/quicklisp/quicklisp-bootstrap/issues/17</a>&= nbsp;</div><br class=3D""><div class=3D"">I got the bootstrap working = mainly by using #+mcl and #-mcl to conditionalize the CCL support, and I = think there was one thing I had to tweak in 5.1 in the defpackage call = because MCL didn=E2=80=99t support one option.</div><div class=3D""><br = class=3D""></div><div class=3D"">I had to do a little more in MCL 3.4, = since there were a couple of issues with using its binary TCP binary = stream but those should probably be patches to MCL 3.4 since they just = seemed like implementation bugs=E2=80=A6 Of course, I need to figure out = how to make and use MCL patches, but how hard could that be? = :)</div><div class=3D""><br class=3D""></div><div class=3D""> -- = Chris</div><div class=3D""><br class=3D""></div></body></html>= --Apple-Mail=_AABB7D52-A1EE-4381-81BE-45DE08A72006-- --===============8725354823510240881== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KaW5mby1tY2wg bWFpbGluZyBsaXN0CmluZm8tbWNsQGNsb3p1cmUuY29tCmh0dHBzOi8vbGlzdHMuY2xvenVyZS5j b20vbWFpbG1hbi9saXN0aW5mby9pbmZvLW1jbAo= --===============8725354823510240881==--