Well, building the sbcl-1.2.2 sources myself using the sbcl-1.1.8 MacOSX x86_64 binary as the bootstrap LISP interpreter with nothing more than `sh make.sh` succeeded.
It looks like something specific to HomeBrew's installation procedure is causing it. I'm using the same sbcl 1.2.2 source and the same sbcl-1.1.8 bootstrap binary that HomeBrew uses.
It looks like the exact command used by HomeBrew for build is:
./make.sh --prefix=/usr/local/Cellar/sbcl/1.2.2 --xc-host=/private/tmp/sbcl--bootstrap64-0pUAlH/sbcl-1.1.8-x86-64-darwin/src/runtime/sbcl --core /private/tmp/sbcl--bootstrap64-0pUAlH/sbcl-1.1.8-x86-64-darwin/output/sbcl.core --disable-debugger --no-userinit --no-sysinit
When I try running that myself, I"m told "--core" is an unknown make-config.sh option. It looks like I need to go over to HomeBrew and file a bug to better understand what they're doing.
Well, building the sbcl-1.2.2 sources myself using the sbcl-1.1.8 MacOSX x86_64 binary as the bootstrap LISP interpreter with nothing more than `sh make.sh` succeeded.
It looks like something specific to HomeBrew's installation procedure is causing it. I'm using the same sbcl 1.2.2 source and the same sbcl-1.1.8 bootstrap binary that HomeBrew uses.
It looks like the exact command used by HomeBrew for build is: /usr/local/ Cellar/ sbcl/1. 2.2 --xc-host= /private/ tmp/sbcl- -bootstrap64- 0pUAlH/ sbcl-1. 1.8-x86- 64-darwin/ src/runtime/ sbcl --core /private/ tmp/sbcl- -bootstrap64- 0pUAlH/ sbcl-1. 1.8-x86- 64-darwin/ output/ sbcl.core --disable-debugger --no-userinit --no-sysinit
./make.sh --prefix=
When I try running that myself, I"m told "--core" is an unknown make-config.sh option. It looks like I need to go over to HomeBrew and file a bug to better understand what they're doing.