[Pharo-fuel] [Vm-dev] Fwd: Possible collections problem

David T. Lewis lewis at mail.msen.com
Fri May 17 02:47:32 UTC 2013

On Thu, May 16, 2013 at 08:06:39PM +0100, Frank Shearar wrote:
> On 16 May 2013 20:01, David T. Lewis <lewis at mail.msen.com> wrote:
> >
> > On Thu, May 16, 2013 at 07:55:39PM +0200, Max Leske wrote:
> >>
> >> I nearly went insane because of Ruby. Debian might be stable but you never get the new stuff? The result were several ours of trying to run "bundle install; rake build" until I finally just tried running "build_interpreter_vm.sh" and HURRAY! I had a working 4.12.4-2729 version.
> >>
> >
> > Instructions for building a standard Interpreter VM for Unix, including generation
> > of the VM sources, can be found at http://squeakvm.org/unix/devel.html. It's worth
> > reading this just to get an overview of the process (regardless of whether you use
> > a Ruby script or any other procedure).
> >
> > If you prefer just compiling from a known-good tarball, the latest official release
> > (which should be fine for your purposes) is on squeakvm.org at
> > http://squeakvm.org/unix/release/Squeak-
> That's exactly what build_interpreter_vm.sh and rake build do - pull
> down that particular tarball, and run the make in platforms/unix. The
> advantage of the rake build is that, since Ruby is a far superior
> scripting language to shell, it'll do the right thing in a bunch of
> different places, depending on your OS.
> Ah, actually, build_interpreter_vm.sh builds _the latest_ VM (as in
> the output of build.squeak.org's InterpreterVM job). rake build builds
> _the latest released VM_.

Yes, I understand. But I also want people to know how to find the information
on squeakvm.org. After all, it only takes a couple of minutes to read it, and
spending a few minutes to learn the basics can save a lot of time and frustration
if something does not work as expected.


More information about the Vm-dev mailing list