From: Stas B. <sta...@gm...> - 2008-05-17 06:56:47
|
When sb-fluid is enabled I get the following error: "[building initial core file in "output/cold-sbcl.core": writing 8192 bytes [2 pages] from #<SB!FASL::GSPACE :READ-ONLY> writing 4096 bytes [1 page] from #<SB!FASL::GSPACE :STATIC> writing 50475008 bytes [12323 pages] from #<SB!FASL::GSPACE :DYNAMIC> /(DESCRIPTOR-BITS INITIAL-FUN)=#X10028ACAE9 done] * //testing for consistency of first and second GENESIS passes //header files match between first and second GENESIS -- good real 5m31.552s user 5m20.128s sys 0m11.413s //entering make-target-2.sh //doing warm init - compilation phase This is SBCL 1.0.16.34, an implementation of ANSI Common Lisp. Argh! error in cold init, halting fatal error encountered in SBCL pid 24922: %PRIMITIVE HALT called; the party is over." Both, host & target, SBCL versions are 1.0.16.34. gcc 4.2.4 20080512 (prerelease) (Debian 4.2.3-6) on x86_64 system gcc 4.2.3 on x86 -- With Best Regards, Stas. |
From: Nikodemus S. <nik...@ra...> - 2008-05-17 09:38:02
|
On Sat, May 17, 2008 at 9:56 AM, Stas Boukarev <sta...@gm...> wrote: > When sb-fluid is enabled I get the following error: SB-FLUID being broken is a know issue (#206 in BUGS) -- but thanks for the report. Apropos, fixing the fluid build is actually pretty simple, just terribly tedious. Approximately: 1. Mechanically rename every #-SB-FLUID to #-OLD-SB-FLUID. 2. Build with :SB-FLUID in features. To verify it works. 3. Convert a bunch of OLD-SB-FLUIDs back to SB-FLUID, and try to rebuild. 4. If it worked, and there are still OLD-SB-FLUIDs left, go to 3. 5. If it didn't work, half of the last batch back, and rebuild. Continue to narrow down till you know which ones broke the build, then delete those, and goto 3. I have a tree where I've been making extremely slow progress along these lines somewhere, but it is several months stale. If someone is interested in working on this, I can put it up somewhere. Cheers, -- Nikodemus |
From: Leonardo V. <va...@gm...> - 2008-05-17 12:52:16
|
I volunteer to do it. On Sat, May 17, 2008 at 6:37 AM, Nikodemus Siivola <nik...@ra...> wrote: > On Sat, May 17, 2008 at 9:56 AM, Stas Boukarev <sta...@gm...> wrote: >> When sb-fluid is enabled I get the following error: > > SB-FLUID being broken is a know issue (#206 in BUGS) -- but thanks for > the report. Apropos, fixing the fluid build is actually pretty simple, > just terribly tedious. Approximately: > > 1. Mechanically rename every #-SB-FLUID to #-OLD-SB-FLUID. > 2. Build with :SB-FLUID in features. To verify it works. > 3. Convert a bunch of OLD-SB-FLUIDs back to SB-FLUID, and try to rebuild. > 4. If it worked, and there are still OLD-SB-FLUIDs left, go to 3. > 5. If it didn't work, half of the last batch back, and rebuild. > Continue to narrow > down till you know which ones broke the build, then delete those, and goto 3. > > I have a tree where I've been making extremely slow progress along > these lines somewhere, but it is several months stale. If someone is > interested in working on this, I can put it up somewhere. > > Cheers, > > -- Nikodemus > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel > -- The most fundamental particles in this product are held together by a "gluing" force about which little is currently known and whose adhesive power can therefore not be permanently guaranteed. |
From: Sidney M. <si...@si...> - 2008-05-17 14:10:42
|
Leonardo Varuzza wrote, On 18/5/08 12:52 AM: > I volunteer to do it. Hold up a bit... I've automated the test and I'm running it now, building with just one file at a time having sb-fluid enabled. So far I have seen that the build ends up in LDB if src/code/bignum.lisp is the only one compiled with sb-fluid. The test should be finished in a few hours. -- sidney |
From: Sidney M. <si...@si...> - 2008-05-17 18:25:09
|
There are two files that break the build when either or both have sb-fluid enabled. If I edit those two files to rename the symbol in #!-sb-fluid to #!-sb-fluid-foo then the build completes ok and passes all tests that it usually passes. The offending files are src/code/bignum.lisp with six instances of #!-sb-fluid src/code/target-sxhash.lisp with one instance of #!-sb-fluid -- sidney |
From: Nikodemus S. <nik...@ra...> - 2008-05-17 20:05:16
|
On Sat, May 17, 2008 at 9:24 PM, Sidney Markowitz <si...@si...> wrote: > There are two files that break the build when either or both have sb-fluid > enabled. If I edit those two files to rename the symbol in #!-sb-fluid to > #!-sb-fluid-foo then the build completes ok and passes all tests that it > usually passes. > > The offending files are > > src/code/bignum.lisp with six instances of #!-sb-fluid > src/code/target-sxhash.lisp with one instance of #!-sb-fluid Thanks for tracking this down! SB-FLUID build new works again in SBCL 1.0.16.37. Cheers, -- Nikodemus |