Known Problems with Gforth 0.6.2

(mostly about installation).

Build problem on Fedora Core 1 (or any system with exec-shield)

Symptoms

The build fails with

 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=32D0E0
 code
 in file included from *the terminal*:0
 *evaluated string*:-1: images produced by different engines
 ...

Fix
 Apply the following patch:

 Index: comp-i.fs
 ===================================================================
 RCS file: /usr/local/lib/cvs-repository/src-master/gforth/comp-i.fs,v
 retrieving revision 1.14
 diff -u -r1.14 comp-i.fs
 --- comp-i.fs	2003/08/25 14:17:43	1.14
 +++ comp-i.fs	2004/03/10 16:26:46
 @@ -43,7 +43,7 @@
      if
  	." : images have the same base address; producing only a data-relocatable  image" cr
      else
 -	offset abs expected-offset <> abort" images produced by different  engines"
 +	\ offset abs expected-offset <> abort" images produced by different  engines"
  	."  offset=" offset . cr
  	0 image1 i-field + ! 0 image2 i-field + !
      endif

Explanation
 Data allocation varies more between the runs than it does without exec-shield.