Re: [Sbcl-bugs] can't compile sbcl-2.6.1 on OpenIndiana SPARC

If your only goal is to bootstrap SBCL, not necessarily to be SBCL-pure 
in your bootstrap chain, you might get some mileage out of bootstrapping 
SBCL with another CL compiler.  E.g. ECL can be built with a pure C 
toolchain, and you can use ECL to compile SBCL by passing

     sh make.sh --xc-host=/path/to/ecl ...



On 1/29/26 4:53 PM, Douglas Katzman via Sbcl-devel wrote:
> 
> On Thu, Jan 29, 2026 at 3:22 PM Klaus Ziegler via Sbcl-bugs <sbcl- 
> [email protected] <mailto:[email protected]>> wrote:
> 
> 
> 
>     Would it also be possible to make my way up the
>     chain from 2.0.4 - 2.1.1 and so on...
> 
> That may be possible in theory, but you're talking about stepping 
> through 5 years of evolution with either 1 build per release or guessing 
> how many months ahead you can jump before exposing a bug in the previous 
> release.
> But aside from the tedium, you may hit problems with the older C 
> runtime.    As a quick feasibility exercise, I went on a SunOS GCC farm 
> machine, downloaded the prebuilt SBCL as you did, and I tried building 
> 2.0.11 which failed in the C compile.
> I think you'll probably have an easier time using a known good (current) 
> aarch64 or x86-64 host and doing a cross-build.




_______________________________________________
Sbcl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-devel