5 ms·

SBCL documentation states that it can be built with another Lisp, but that is not true: I've tried with CCL and it failed spectacularly. I couldn't find a work

SBCL documentation states that it can be built with another Lisp, but that is not true: I've tried with CCL and it failed spectacularly. I couldn't find a working version of CLISP for Solaris 10 for sparc and i86pc. Guys, I've built hundreds of packages for Solaris 10 on both sparc and i86pc the number of which can easily compete with the number of packages on "OpenCSW" and I'm telling you that SBCL is so broken on the operating system from which it came that it can no longer be built or run on it without the involvement of the core SBCL team. It needs serious attention.

rjsw 7y ago
CLISP should build from source, it seems to be getting built fine by Joyent pkgsrc bulk builds. Their build of SBCL is failing in C code [1], maybe a Solaris expert could fix this. The usual reason that SBCL stops building is that something has changed in the OS. [1] http://us-east.manta.joyent.com/pkgsrc/public/reports/upstream-trunk64/20190715.0211/sbcl-1.4.3nb1/build.log http://us-east.manta.joyent.com/pkgsrc/public/reports/upstre...
- Annatar 7y ago
  But nothing has changed on my build servers which are running Solaris 10, so OS change cannot be the cause; without additional information, that leaves us with one or more breakage(s) caused by someone in the core SBCL team.
  - rjsw 7y ago
    Did you look at the build log I posted ?
    - Annatar 7y ago
      I sure did: it's due to changing the code but not using the correct macro definitions and compiler options from what I could see (I'm on a mobile telephone, on vacation, so lots of the log is cut off). But you also have to realize that Solaris 10 is much older than illumos and I'm telling you that the build breaks on both. I actually patched that and got past it, half a year ago. The build broke somewhere else after that and it was in Lisp so I had no idea how to fix it. This breakage is just a simple endianess "pre-flight check". SBCL's problems are much more serious then this: they broke it but good.

rjsw 7y ago

CLISP should build from source, it seems to be getting built fine by Joyent pkgsrc bulk builds. Their build of SBCL is failing in C code [1], maybe a Solaris expert could fix this. The usual reason that SBCL stops building is that something has changed in the OS. [1] http://us-east.manta.joyent.com/pkgsrc/public/reports/upstream-trunk64/20190715.0211/sbcl-1.4.3nb1/build.log http://us-east.manta.joyent.com/pkgsrc/public/reports/upstre...

Annatar 7y ago
But nothing has changed on my build servers which are running Solaris 10, so OS change cannot be the cause; without additional information, that leaves us with one or more breakage(s) caused by someone in the core SBCL team.
- rjsw 7y ago
  Did you look at the build log I posted ?
  - Annatar 7y ago
    I sure did: it's due to changing the code but not using the correct macro definitions and compiler options from what I could see (I'm on a mobile telephone, on vacation, so lots of the log is cut off). But you also have to realize that Solaris 10 is much older than illumos and I'm telling you that the build breaks on both. I actually patched that and got past it, half a year ago. The build broke somewhere else after that and it was in Lisp so I had no idea how to fix it. This breakage is just a simple endianess "pre-flight check". SBCL's problems are much more serious then this: they broke it but good.