[Larceny-users] Larceny 0.961 build annoyances

David Rush kumoyuki at gmail.com
Sat Jun 21 14:47:31 EDT 2008


HI y'all -

I don't know what it is with my Debian systems, but I seem to have
endless problems building Larceny on them. My latest round has
occurred with the 0.961 source code tarball. I can't use the binary
release because of libc incompatibility with my Debian Etch release,
so I just moved on to building the code from source, hosting it on PLT
v372.

The build went fine up until sasstrap.heap got dumped. Then I get:

  Dumping sasstrap.heap
  Loading src/Lib/Common/malcode.lop

  *** Error encountered!
  Deleting target file: sasstrap.heap
  make-sasstrap-heap: sasstrap.heap

   === context ===
  select-handler/no-breaks
  /home/drr/dist/larceny-0.961-src/src/Build/make.sch:351:2: make
  /home/drr/dist/larceny-0.961-src/src/Build/make.sch:244:0: make:make

  >

Continuing on from there (figuring that I can grab the heap images
from the binary dist)

  (build-runtime)
  (build-executable)

both ran perfectly. So I copied them into my 0.961 binary distribution
directory and voilá - a working larceny system. So can anybody tell me
why I am having issues building the heaps? This is actually not the
first time this has occurred to me, but I had downstream issues with
ERR5RS which caused me to believe that I needed to rebuild the
libraries as well (as in step 4 from HOWTO-BUILD) and *that* build
failed while trying to load syntax-case saying that there was a
version mismatch between the expanders (or some such - I don't have it
here right now).  I would very much like to know what I need to change
in order to get a clean build.

And FWIW, I am not stuck. My ERR5RS problems turned out to be operator
error compounded by impure installation steps. The problem building
the heaps is quite reproducible for me. SO this qualifies as merely an
annoyance. As is the fact that - for whatever reason - I *still* can't
get a clean build of the runtime under x86-64. but that's a different
story and not exceedingly relevant as my deployment host is only 32
bits. What are the chances of a 64-bit native Larceny for this summer?

david rush
-- 
GPG Public key at http://cyber-rush.org/drr/gpg-public-key.txt



More information about the Larceny-users mailing list