Skip to main content

Install current SBCL on OS X

You must have Command Line Tools installed. If you don't, this tutorial is not for you. Google: installation of XCode and Command Line Tools.

Normally, I use brew to install things (when it offers a solution), but in this case the keg version was a couple minor version's off. And, there had been sufficient addition's that motivated me to want the current release. So, building from source was the path of least resistance.

First, what not to do:

The note's caution against using OS X's Terminal, as their make.sh script pukes a shit-ton of text during the build, and according to them, it can slow the build. I did not experience an issue with this, compared to other builds I've done in the past.  BUT, they also say build can be accomplished with other LISP's installed (you must have a lisp installed prior to building). OMFG, unless you want to wait a month of Sunday's, my experience building with CLISP was slower than the Molasses in January.  Do yourself a favor if you don't have an install of sbcl already  (likely from brew as it is a few minor version's behind the current one at this time), install sbcl from brew FIRST!!!  Build went so much faster.

So, here's what I recommend:

Install sbcl using brew.  If you don't already have brew installed, why the frak not?  Install it. You can thank me later.

Ok, so you've installed sbcl using brew. Now, download the current version from sbcl's website,  untar/unbzip it, and cd into the new directory. For illustrative purposes, in my case it's /sbcl-1.2.5. Once inside, you can follow their prescribed method (you may need to sudo first):

sh make.sh

It will pick-up the current install of sbcl and use it. Once it's done, uninstall brew's version of sbcl:

brew uninstall sbcl

Now, (again, you may need to sudo first):

sh install.sh

You should now have the current sbcl available in your path at:

/usr/local/bin/sbcl

Comments

Popular posts from this blog

Kicking things off

My purpose here is to document various thoughts and findings as things come up, or come to mind.  All strictly technical, and kind of a development diary of sorts.  While ideally, others may find these things useful, my main intent is to have them here for my reference ;-) Still, I'll try to write them in tutorial fashion

Add pre-compiled Elixir on OS X

So, I've been a big Erlang fan for a few years now, and then found out about Elixir :  what I would describe as kind of a Ruby -ish creamy frosting on top of Erlang . But I'll address more on both in future. Right now, I thought I'd just give a quick and dirty way to add Elixir , if you've already got Erlang installed (hint: check-out this Erlang Solutions link for a pre-compiled Erlang solution).  You can also use brew to install both , but I have found that with the simplicity of brew, you give up having the most current version of software.  In both cases. The pre-compiled zip for the most current version of  Elixir can be found here .  Unzipping reveals a folder containing everything you need.  For simplicity's sake, keeping everything pertaining to Elixir all within this folder makes the most sense.  By doing so, all that's needed is to position the folder, and then make links to all the executables in a directory already in our path.  Through t...

Passing Functions and Lambdas into Functions with Ruby

Ruby's New Style of Lambda Functions f = ->( m ) { p m } f.call( 1 ) #=> 1 Which of course means the same thing as: f = lambda { |n| p n } f.call(1) #=> 1 Ruby Proc Objects p = Proc.new { |n| p n + 2 } p.call(2) #=> 4 Using a Function as a Closure in Ruby def domo( k ) ->(m) { p m + k } end z = domo( 5 ) z.call( 5 ) #=> 10 Function :domo takes a single parameter. Within :domo , we create a lambda that takes a single parameter, and adds that parameter to the value :domo takes in as its parameter. Then, we assign z to be the result of the lambda in :domo with its 'k' parameter loaded with 5. When z is called, we pass (another) 5 to it. This parameter loads the lambdas n parameter. The lambda executes, essentially adding n (5) + k (5) and yielding the result of 10. The thing about closures such as this is, we can load the initial value of the lambda to be whatever we want it to be when assigning the function :domo '...