This is a collection of all the compilation tools necessary to
compile an ANSI C program, (except hardware drivers and
initialization routines) for the CRIS architecture (ETRAX
chips), and make "clean" binary files of the linked output.

To configure, compile and install:
./install-cris-tools [target-lib-binary-dir [execution-binary-dir
  [man-dir [info-dir [temp-dir [install-root]]]]]]]

(You may specify /dev/null for man-dir or info-dir if you do not
want documentation.)

The compiler parts (including header files) will be installed under
target-lib-binary-dir.  The compiler tools will be installed under
execution-binary-dir.  Temporary files such as object files will be located in
temp-dir; it defaults to "./tmpdir".

The last option, install-prefix, is prepended to all file paths for
"temporary" installation, useful when preparing binary packages.
Since this might be confusing a confusing parameter to interactive users,
it is not presented as a choice in the interactive dialogue.
If an installation prefix is specified, some functionality is skipped,
such as testing permissions on installation paths, testing the installed
compiler and removing any pre-existing installation.

You have to have write permissions in those directories, of course.

If you're opposed to executing unknown shell scripts, then please look in it
and execute the steps manually.  The shell script is provided as a
convenience; it checks details that must not be forgotten and produces a log
to include in email in case things go wrong.

The install script will ask a couple of obvious questions and test for file
access permissions, and presence of a previous installation.

There is also a cris-dist.spec, corresponding to what is used in RPM:s
distributed at <ftp://ftp.axis.se/pub/axis/tools/cris/compiler-kit/>.

If you encounter problems, or have questions regarding these tools, email
<compiler-contact@axis.com>.  But before that, please look at the
error-message in the log for locally induced failures, such as "disk
full".
 Please also note that some NFS configurations (between SUN/Solaris and
Linux) have problems, showing behavior similar to fluky hardware, as
presented in <URL:http://www.bitwizard.nl/sig11/>.


Differences between this and the closest publicly available sources:

- binutils directory: Latest import is from the FSF binutils 2.12.1.
  See <URL:http://sources.redhat.com/binutils/>.  Testsuites for
  architectures other than CRIS may be missing.  Axis-specific
  changes are entered into ChangeLog files named ChangeLog.Axis.

- gnu-toplev/newlib and gnu-toplev/libgloss directories: Latest import is
  the CVS version of 2000-04-27 23:30 CET (see
  <URL:http://sourceware.cygnus.com/newlib/>): "-D 2000-04-27 23:30 CET".
  Changes are logged in files named ChangeLog.Axis.  The "cris"
  directories are new.

- Rest of gnu-toplev: Latest import is (similar to newlib) the
  CVS version from GCC of 2000-04-27 23:30 CET (see
  <URL:http://gcc.gnu.org/cvs.html>).  Changes are logged in
  files named ChangeLog.Axis.  The "cris" directories are new.
  Non-applicable directories (the testsuite, unsupported
  languages and their libraries) are not included.


Some compilation and installation figures (your mileage may vary).
Figures within parenthesis are with glibc compilation included.  An
asterisk is added for outdated numbers:
 45min (1h 45min) 2xPII 512M 350MHz, GNU/Linux-2.2.17, local 10K RPM disks.
 17min    (40min) AMD Athlon 384M 1GHz, GNU/Linux 2.2.17, local 7200 RPM disks.

Disk needs, approximately.  This for a supposedly typically configured x86
GNU/Linux system.  Figures in parentheses includes glibc:
   50M  (100M) Compiler libraries, tool binaries, header files.
    3M    (7M) Info and manual-pages
  190M  (510M) Temporaries

Note that GNU make is required.  Additionally, if glibc is included, a
GNU host system is required.

/Best regards
Axis Communications
