From: Peter V. E. <pva...@de...> - 2005-11-05 13:42:58
|
Hello I managed to cross compile sbcl 0.9.6.0 with clisp 2.35 with a slight gotcha: the shell has to be bash. If you use sh you get a gc invariant lost ?!? Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| |
From: Rex D. <rd...@ma...> - 2005-11-07 18:04:49
|
Peter Van Eynde wrote: > I managed to cross compile sbcl 0.9.6.0 with clisp 2.35 with a slight gotcha: > the shell has to be bash. If you use sh you get a gc invariant lost ?!? Didn't work for me (on Fedora Core 3 anyway), using clisp-2.35. Tail end of of the build went: ... [building initial core file in "output/cold-sbcl.core": writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :READ-ONLY> writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :STATIC> writing 36188160 bytes [8835 pages] from #<SB!FASL::GSPACE :DYNAMIC> /(DESCRIPTOR-BITS INITIAL-FUN)=#XA3F802D done] Bye. //testing for consistency of first and second GENESIS passes //header files match between first and second GENESIS -- good real 47m56.114s user 36m25.580s sys 8m14.640s + sh -x make-target-2.sh + set -e + echo //entering make-target-2.sh //entering make-target-2.sh + LANG=C + LC_ALL=C + export LANG LC_ALL + echo //doing warm init //doing warm init + ./src/runtime/sbcl --core output/cold-sbcl.core --sysinit /dev/null --userinit /dev/null This is SBCL 0.9.6, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. fatal error encountered in SBCL pid 18509(tid 3086886592): %PRIMITIVE HALT called; the party is over. The system is too badly corrupted or confused to continue at the Lisp level. If the system had been compiled with the SB-LDB feature, we'd drop into the LDB low-level debugger now. But there's no LDB in this build, so we can't really do anything but just exit, sorry. |
From: Peter V. E. <pva...@de...> - 2005-11-08 20:59:57
|
On Monday 07 November 2005 19:02, Rex Dieter wrote: > Peter Van Eynde wrote: > > I managed to cross compile sbcl 0.9.6.0 with clisp 2.35 with a slight > > gotcha: the shell has to be bash. If you use sh you get a gc invariant > > lost ?!? > > Didn't work for me (on Fedora Core 3 anyway), using clisp-2.35. Tail > end of of the build went: ... After retrying it a few times, I notice that sometimes I would just start failing, seemingly depending on some external factor. darcs claims I did no changes, but still the rebuild fails. But the error isn't: > fatal error encountered in SBCL pid 18509(tid 3086886592): > %PRIMITIVE HALT called; the party is over. but a gc invariant that gets lost. Groetjes, Peter -- signature -at- pvaneynd.mailworks.org http://www.livejournal.com/users/pvaneynd/ "God, root, what is difference?" Pitr | "God is more forgiving." Dave Aronson| |
From: Juho S. <js...@ik...> - 2005-11-09 05:50:42
|
<pva...@de...> wrote: > On Monday 07 November 2005 19:02, Rex Dieter wrote: >> Peter Van Eynde wrote: >> > I managed to cross compile sbcl 0.9.6.0 with clisp 2.35 with a slight >> > gotcha: the shell has to be bash. If you use sh you get a gc invariant >> > lost ?!? >> >> Didn't work for me (on Fedora Core 3 anyway), using clisp-2.35. Tail >> end of of the build went: > ... > > After retrying it a few times, I notice that sometimes I would just start > failing, seemingly depending on some external factor. darcs claims I did no > changes, but still the rebuild fails. That matches my experience. Testing since your original report has seen working builds, ones that crash in cold init, and ones where the host clisp dies. > But the error isn't: > >> fatal error encountered in SBCL pid 18509(tid 3086886592): >> %PRIMITIVE HALT called; the party is over. > > but a gc invariant that gets lost. I expect those are essentially the same error. If a GC problem isn't noticed at gc-time, it'll generally lead to a quick crash soon afterwards. -- Juho Snellman |