[movitz-devel] Warning: Auto-bootstrapping CLOS completed.

[Paavo Parkkinen]

I did a fresh install into a formatted / and /home. The first time I
tried creating a new image, I did it in a backup of my old home
directory, but the next time was in the fresh home directory with a
fresh movitz check out.

p

2008/11/8 rob levy <r.p.levy at gmail.com>:
> This is probably way off, but if you installed the new version of Ubuntu and
> it upgraded SBCL, then you may need to delete stale FASLs.
>
> Rob
>
> On Sat, Nov 8, 2008 at 6:59 AM, Paavo Parkkinen <pparkkin at iki.fi> wrote:
>>
>> 2008/11/7 Andreas Davour <ante at update.uu.se>:
>> > On Fri, 7 Nov 2008, Paavo Parkkinen wrote:
>> >
>> >> I compiled and dumped the los0 image with SBCL, and booted it with
>> >> qemu like I've done many times before, only this time I got this:
>> >>
>> >> Enter..Ok.
>> >> Installing los0-GC with 63238 KB.
>> >> Break: Auto-bootstrapping CLOS.
>> >> Warning: Auto-bootstrapping CLOS completed.
>> >> 0: Return from break: Auto-bootstrapping CLOS.
>> >> [0d] LOS0> 0
>> >> Warning: CLOS was already bootstrapped: T
>> >> Warning: Auto-bootstrapping CLOS completed.
>> >> Error: Out of memory. Please take out the garbage.
>> >> [0d] LOS0>
>> >>
>> >> Only thing I can think of that's changed is, I installed the new
>> >> version of Ubuntu recently. Any idea what might have changed or if I'm
>> >> maybe missing something?
>> >
>> > I don't think I can help out, but interesting information nevertheless
>> > would
>> > be if this is from cvs or the git repository and when did you check out?
>>
>> First time I got the Warnings with a pretty old cvs check out. After
>> that I did a fresh check out and got the same result.
>>
>> p
>>
>> _______________________________________________
>> movitz-devel site list
>> movitz-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/movitz-devel
>
>