From burton.samograd at gmail.com Fri Jul 23 04:14:49 2010 From: burton.samograd at gmail.com (Burton Samograd) Date: Thu, 22 Jul 2010 22:14:49 -0600 Subject: [movitz-devel] Booting LOS0 Failure Message-ID: <84d3uebzra.fsf@gmail.com> Hi, I've been a bit interested in movitz again lately, so I downloaded the git sources and compiled and dumped LOS0 using CLISP 2.48. This all went well, but when I tried to run the image I got the following: http://imgur.com/A8Iwl I tried looking through the code to see what happened, but the most I could come up with was that maybe *all-process* was empty during the call to (LIB::CURRENT-PROCESS). Other than that I'm stumped. Any idea what is happening? -- Burton Samograd From burton at userful.com Fri Jul 23 15:04:03 2010 From: burton at userful.com (Burton Samograd) Date: Fri, 23 Jul 2010 09:04:03 -0600 Subject: [movitz-devel] Booting LOS0 Failure References: <84d3uebzra.fsf@gmail.com> Message-ID: "Burton Samograd" writes: I tried building Movitz on a linux system using SBCL 1.0.29.11 and it worked and ran fine. I seem to remember that CLISP wouldn't even dump the image properly in the past without crashing, so I guess there's still some errors when using it to build movitz. > Hi, > > I've been a bit interested in movitz again lately, so I downloaded the > git sources and compiled and dumped LOS0 using CLISP 2.48. This all > went well, but when I tried to run the image I got the following: > > http://imgur.com/A8Iwl > > I tried looking through the code to see what happened, but the most I > could come up with was that maybe *all-process* was empty during the > call to (LIB::CURRENT-PROCESS). Other than that I'm stumped. -- Burton Samograd