Diff for /gforth/INSTALL between versions 1.35 and 1.39

version 1.35, 2003/08/25 14:17:43 version 1.39, 2008/07/26 20:57:05
Line 1 Line 1
 Copyright (C) 2003 Free Software Foundation, Inc.  Copyright (C) 2003,2007 Free Software Foundation, Inc.
 This file is free documentation; the Free Software Foundation gives  This file is free documentation; the Free Software Foundation gives
 unlimited permission to copy, distribute and modify it.  unlimited permission to copy, distribute and modify it.
   
   
                 Prerequisites                  Prerequisites
   
 You need gcc version 2.0 or later to compile gforth.  Recommended:  You need gcc version 2.0 or later to compile gforth.
 gcc-2.95.* (other versions produce slower code).  
   
 To use the new C interface, you need to install the ffcall libraries  For the (documented) libcc.fs C interface you need a C compiler at
 before configuring Gforth.  You can find them on  run-time.
   
   For the (undocumented ) lib.fs C interface you need to install either
   the ffcall libraries or the libffi library.  Libffi comes with recent
   gccs, ffcall can be found on
   
    ftp://ftp.santafe.edu/pub/gnu/ffcall-1.8.tar.gz (USA)      ftp://ftp.santafe.edu/pub/gnu/ffcall-1.8.tar.gz (USA) 
    ftp://ftp.ilog.fr/pub/Users/haible/gnu/ffcall-1.8.tar.gz (Europe)      ftp://ftp.ilog.fr/pub/Users/haible/gnu/ffcall-1.8.tar.gz (Europe) 
   
   On many architectures (exceptions: 386, PPC, MIPS, Alpha) you need gdb
   at run-time in order for the disassembler to work.
   
   
                 Building and Installing                  Building and Installing
   
Line 27  After configuration, type Line 33  After configuration, type
   
 make  make
   
 Now you can check whether your shiny new Forth system works. Say  This includes a check whether your shiny new Forth system works. If
   you like to invoke the check alone, do
   
 make check  make check
   
Line 131  You need a cross-compilation toolchain f Line 138  You need a cross-compilation toolchain f
 The first step in cross-installation is the cross-configuration.  A  The first step in cross-installation is the cross-configuration.  A
 few tests made by the configure script do not work in a  few tests made by the configure script do not work in a
 cross-compilation situation. You have to provide the results of these  cross-compilation situation. You have to provide the results of these
 tests by hand. E.g., if you compile for a 386 architecture processor:  tests by hand. E.g., if you compile for an ARM:
   
 env ac_cv_sizeof_char_p=4 ac_cv_sizeof_char=1 ac_cv_sizeof_short=2 ac_cv_sizeof_int=4 ac_cv_sizeof_long=4 ac_cv_sizeof_long_long=8 ac_cv_sizeof_intptr_t=4 ac_cv_sizeof_int128_t=0 ac_cv_c_bigendian=no ./configure  env skipcode=".skip 16" ac_cv_sizeof_char_p=4 ac_cv_sizeof_char=1 \
   ac_cv_sizeof_short=2 ac_cv_sizeof_int=4 ac_cv_sizeof_long=4 \
   ac_cv_sizeof_long_long=8 ac_cv_sizeof_intptr_t=4 ac_cv_sizeof_int128_t=0 \
   ac_cv_c_bigendian=no ./configure CC=arm-elf-gcc --host=arm-linux
   
 The ac_cv_sizeof_... variables give the sizes of various C types;  The ac_cv_sizeof_... variables give the sizes of various C types;
 ac_cv_sizeof_char_p is the same as "sizeof(char*)" in C code. The  ac_cv_sizeof_char_p is the same as "sizeof(char*)" in C code. The
 ac_cv_c_bigendian variable gives the byte order.  ac_cv_c_bigendian variable gives the byte order.  The skipcode
   specifies how to skip 16 bytes in the code (use "skipcode=no" to
   disable skipping and dynamic native code generation).
   
 After the cross-configuration you type  After the cross-configuration you type
   

Removed from v.1.35  
changed lines
  Added in v.1.39


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>