=?ISO-8859-1?Q?Jorge_Acereda_Maci=E1?= wrote: > > I am doing some tests before packaging gforth for fink. This is what I > get: > > $ ./configure CC=gcc2 > ... > $ make > ... > ./gforth --die-on-signal -m 4M -p ".:~+:." -i kernl32b.fi -e 3 > exboot.fs -e 'fpath= .|~+|.' -e 's" mach16b.fs"' ./kernel/main.fs -e > "save-cross kernl16b.fi- /usr/local/bin/gforth-0.6.0 bye" > redefined NIL > in file included from *the terminal*:0 > in file included from kernel/main.fs:92 > in file included from kernel/kernel.fs:24 > kernel/int.fs:733: CROSS: forward > ['] cr catch if > ^^ > Backtrace: > $F4BA4 throw > $362BCC c(abort") > $3681D8 g>xt > $368220 ' > $3621BC execute > $3689E8 execute-exec-compile > $368C20 tcom > $368C9C ] > $368D10 (:) > make: *** [kernl16b.fi-] Error 1 > > Any idea on what's going on there?
I saw some Heisenbugs in earlier testing on big-endinan machines (on several architectures and OSs). Thay always occured when building kernel images, and did not produce a useful error message. After adding "-e 3 exboot.fs", at least the last problem is solved. The failures went away at the slightest provocation (e.g., adding (IIRC) '-e "100 allocate 2drop"' as the first image option). Unfortunately, my latest tests did not reproduce this bug, either, despite having 6 big-endian machines in my test base. I hope that this bug only occurs during cross-compilation (then everything would be all right as soon as we get past that stage). I will have to reproduce it and probably use gdb or somesuch to exterminate it. But maybe our cross.fs specialists can say more about that? - anton --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
