--- gforth/INSTALL 2003/03/09 17:16:38 1.34 +++ gforth/INSTALL 2008/10/13 20:20:56 1.40 @@ -1,9 +1,28 @@ -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 unlimited permission to copy, distribute and modify it. + + Prerequisites + You need gcc version 2.0 or later to compile gforth. +For the (documented) libcc.fs C interface you need a C compiler and +libtool at 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.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 + First, type ./configure @@ -14,7 +33,8 @@ After configuration, type 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 @@ -68,14 +88,10 @@ configure has the following useful param [default: /usr/local] --exec-prefix=PREFIX install architecture-dependent files in PREFIX [default: same as prefix] - --enable-force-reg Use explicit register declarations if they appear in - the machine.h file. This can cause a good speedup, - but also incorrect code with some gcc versions on - some processors (default disabled). --help: tells you about other parameters. -The file Benchres shows which combination of the -enable options we -tried gave the best results for various machines. +The file Benchres shows the best gforth-fast performance that we +achieved. If you don't like the defaults for the installation directories, you should override them already during configure. E.g., if you want to @@ -87,18 +103,18 @@ hierarchy, say Moreover, if your GCC is not called gcc (but, e.g., gcc-2.7.1), you should say so during configuration. E.g.: -env CC=gcc-2.7.1 ./configure +./configure CC=gcc-2.7.1 You can also pass additional options to gcc in this way, e.g., if you want to generate an a.out executable under Linux with gcc-2.7.0: -env "CC=gcc -b i486-linuxaout -V 2.7.0" ./configure +./configure CC="gcc -b i486-linuxaout -V 2.7.0" You can change the sizes of the various areas used in the default image `gforth.fi' by passing the appropriate Gforth command line options in the FORTHSIZES environment variable: -env "FORTHSIZES=--dictionary-size=256k --data-stack-size=16k --fp-stack-size=15872b --return-stack-size=15k --locals-stack-size=14848b" ./configure +./configure "FORTHSIZES=--dictionary-size=1048576 --data-stack-size=16k --fp-stack-size=16K --return-stack-size=15k --locals-stack-size=14848b" The line above reaffirms the default sizes. Note that the locals stack area is also used as input buffer stack. @@ -107,54 +123,45 @@ If C's "long long" do not work properly tests involving double-cell numbers fail), you can build Gforth such that it does not use "long long": -env ac_cv_sizeof_long_long=0 ./configure +./configure ac_cv_sizeof_long_long=0 + +For MacOS X on Core 2 processors, you might want to use the 64-bit +version for increased speed (more registers available); you have to +ask for that on configuration, as follows: + +./configure CC='gcc-4.2 -arch x86_64' --build=x86_64-apple-darwin9.4.0 Cross-Installation +There is currently no simple way to do cross-installation of Gforth +(apart from Gforth EC). The current build process interleaves +compiling and running heavily, so multiple transfers between build and +target machine would be required. We don't have a testing environment +for cross-compilation, so we cannot fix this at the moment. If you +want to do cross-installation, please contact us. + +In any case, you might find the following useful: + You need a cross-compilation toolchain for your target including gcc (2.0 or later). The first step in cross-installation is the cross-configuration. A few tests made by the configure script do not work in a 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_void_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_sizeof_uint128_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; ac_cv_sizeof_char_p is the same as "sizeof(char*)" in C code. The -ac_cv_c_bigendian variable gives the byte order. - -After the cross-configuration you type - -make gforths - -This produces the gforth engines for the target. - -The next step is to transfer everything to the target; on the target, -you do - -make - -to complete building gforth. If you do not have a make on the target, -run - -make -n - -on the host; manually execute on the target the last command output by -"make -n" (GFORTHD=...); the other commands output by "make -n" are -not necessary unless you have changed the Gforth sources. You can -then check and benchmark Gforth with - -make check -make bench - -or equivalent. Finally, perform - -make install - -or the equivalent commands on the target. +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). Preloading installation-specific code @@ -212,4 +219,3 @@ INFOPATH=/usr/local/info:/usr/info 2. Create a file called 'dir' in 'usr/local/info'. Use the file '/usr/info/dir' as a template. You can add the line for gforth manually, or use '/sbin/install-info' (man install-info for details). -