A build of 0.6.2 (this is the latest stable, right?) on OpenBSD 4.3 ends like this

   `gforth' is up to date.
   `gforth-ditc' is up to date.
   `gforth-fast' is up to date.
   `gforth-itc' is up to date.
   cp -p gforth gforth~
   cp -p engine/gforth gforth
   cp -p kernl32l.fi kernl32l.fi~
   cp -p kernl32l.fi- kernl32l.fi
   cp -p engine/gforth-ditc gforth-ditc
   GFORTHD="./gforth-ditc -p .:." GFORTH="./gforth-ditc --die-on-signal
   -p .:. -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs
   arch/386/disasm.fs" ./gforthmi gforth.fi  --die-on-signal -p
   ".:~+:." -i kernl32l.fi -e 3 exboot.fs startup.fs arch/386/asm.fs
   arch/386/disasm.fs
   data offset=-E11BF20
   code
   in file included from *the terminal*:0
   *evaluated string*:-1: images produced by different engines
   comp-image ./temp-image.fi1 ./temp-image.fi2 gforth.fi bye
                                                ^^^^^^^^^
   Backtrace:
   $46CBBC throw
   $496FB0 c(abort")
   $49724C image-data
   $497924 compare-images
   #echo '2c\' >prim.TAGS.sed
   #echo ./prim >>prim.TAGS.sed
   #./gforth --die-on-signal -p
   
".:/usr/local/lib/gforth/site-forth:/usr/local/share/gforth/site-forth:/usr/local/lib/gforth/0.6.2:/usr/local/share/gforth/0.6.2:."
   prims2x.fs -e "s\" ./prim.b\" ' output-tag dup process-file bye" |
   sed -f prim.TAGS.sed >prim.TAGS-
   ./gforth --die-on-signal -p
   
".:/usr/local/lib/gforth/site-forth:/usr/local/share/gforth/site-forth:/usr/local/lib/gforth/0.6.2:/usr/local/share/gforth/0.6.2:."
   prims2x.fs -e "s\" ./prim.b\" ' output-tag dup process-file bye"
    >prim.TAGS-
   ./gforth: Cannot allocate memory
   *** Error code 1

   Stop in /usr/local/src/GForth/gforth-0.6.2 (line 813 of Makefile).

Any tips? Thanks.

--
Jack J. Woehr            # "Self-delusion is
http://www.well.com/~jax #  half the battle!"
http://www.softwoehr.com #  - Zippy the Pinhead


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to