anchor.diff:  * The Makefiles do not support parallel make (e.g. make -j2).
   Fix: do not pass the -j option to make, and be patient.
   
  -* The Makefiles use the "include" directive, which is not supported by
  -all versions of make. Use GNU make if this is a problem.
  -
  -* Solaris make mishandles a space in our Makefiles, so you have to use GNU
  -make to build on Solaris.
  -
  -* The Makefiles assume that make executes commands by calling /bin/sh. They
  -won't work if /bin/csh is called instead. You may have to unset the SHELL
  -environment variable, or set it to /bin/sh.
  -
  -* On some systems, localization causes build problems.  You should
  -try to set the C locale (export LC_ALL=C) before compiling if you have
  -strange errors while compiling OCaml.
  -
  -* gcc 2.7.2.1 generates incorrect code for the runtime system in -O mode
  -on some Intel x86 platforms (e.g. Linux RedHat 4.1 and 4.2).
  -If this causes a problem, the solution is to upgrade to 2.7.2.3 or above.
  -
  -* Some versions of gcc 2.96 for the Intel x86 (as found in RedHat 7.2,
  -Mandrake 8.0 and Mandrake 8.1) generates incorrect code for the runtime
  -system.  The "configure" script tries to work around this problem.
  -
  -* On HP 9000/700 machines under HP/UX 9.  Some versions of cc are
  -unable to compile correctly the runtime system (wrong code is
  -generated for (x - y) where x is a pointer and y an integer).
  -Fix: use gcc.
  -
  -* Under MacOS X 10.6, with XCode 4.0.2, the configure script mistakenly
  -detects support for CFI directives in the assembler.
  -Fix: give the "-no-cfi" option to configure.
  +* The Makefiles use the `include` directive, which is not supported by all
  +  versions of make. Use GNU Make if this is a problem.
  +
  +* Solaris make mishandles a space in our Makefiles, so you have to use GNU make
  +  to build on Solaris.
  +
  +* The Makefiles assume that make executes commands by calling `/bin/sh`. They
  +  won't work if `/bin/csh` is called instead.  You may have to unset the `SHELL`
  +  environment variable, or set it to `/bin/sh`.
  +
  +* On some systems, localization causes build problems.  You should try to set
  +  the C locale (`export LC_ALL=C`) before compiling if you have strange errors
  +  while compiling OCaml.
  +
  +* GCC 2.7.2.1 generates incorrect code for the runtime system in `-O` mode on
  +  some Intel x86 platforms (e.g. Linux RedHat 4.1 and 4.2). If this causes a
  +  problem, the solution is to upgrade to 2.7.2.3 or above.
  +
  +* Some versions of GCC 2.96 for the Intel x86 (as found in RedHat 7.2,
  +  Mandrake 8.0 and Mandrake 8.1) generate incorrect code for the runtime system.
  +  The `configure` script tries to work around this problem.
  +
  +* On HP 9000/700 machines under HP/UX 9, some versions of `cc` are unable to
  +  compile correctly the runtime system (wrong code is generated for `(x - y)`
  +  where `x` is a pointer and `y` an integer). Fix: use `gcc`.
  +
  +* Under OS X 10.6, with XCode 4.0.2, the `configure` script mistakenly detects
  +  support for CFI directives in the assembler. Fix: give the `-no-cfi` option to
  +  `configure`.
  
positive.code:         make opt > log.opt 2>&1     # in sh
          make opt >& log.opt         # in csh
  
  5. anchor:step-5[] Compile fast versions of the OCaml compilers, by
  compiling them with the native-code compiler (you have only compiled
  them to bytecode so far).  Just do:
  
          make opt.opt
  +
  Later, you can compile your programs to bytecode using ocamlc.opt
  instead of ocamlc, and to native-code using ocamlopt.opt instead of
  ocamlopt.  The ".opt" compilers should run faster than the normal
  compilers, especially on large input files, but they may take longer
  to start due to increased code size.  If compilation times are an issue on
  your programs, try the ".opt" compilers to see if they make a
  significant difference.
  +
  An alternative, and faster approach to steps 2 to 5 is
  
          make world.opt          # to build using native-code compilers
  +
  The result is equivalent to "make world opt opt.opt", but this may
  fail if anything goes wrong in native-code generation.
  
  6. You can now install the OCaml system. This will create the
  following commands (in the binary directory selected during
  autoconfiguration):
  
          ocamlc           the batch bytecode compiler
          ocamlopt         the batch native-code compiler (if supported)
          ocamlrun         the runtime system for the bytecode compiler
          ocamlyacc        the parser generator
          ocamllex         the lexer generator
          ocaml            the interactive, toplevel-based system
          ocamlmktop       a tool to make toplevel systems that integrate
                           user-defined C primitives and OCaml code
          ocamldebug       the source-level replay debugger
          ocamldep         generator of "make" dependencies for OCaml sources
          ocamldoc         documentation generator
          ocamlprof        execution count profiler
          ocamlcp          the bytecode compiler in profiling mode
  +
  and also, if you built them during <<step-5,step 5>>,
  
          ocamlc.opt       the batch bytecode compiler compiled with ocamlopt
          ocamlopt.opt     the batch native-code compiler compiled with ocamlopt
          ocamllex.opt     the lexer generator compiled with ocamlopt
  +
  From the top directory, become superuser and do:
  
          umask 022       # make sure to give read & execute permission to all
          make install
  
  7. Installation is complete. Time to clean up. From the toplevel
  directory, do "make clean".
  
  8. (Optional) The emacs/ subdirectory contains Emacs-Lisp files for an
  OCaml editing mode and an interface for the debugger.  To install
  these files, change to the emacs/ subdirectory and do
  
          make EMACSDIR=<directory where to install the files> install
  +
  
negative.code: 
  == PREREQUISITES
  
  * The GNU C Compiler (gcc) is recommended, as the bytecode interpreter takes
    advantage of GCC-specific features to enhance performance. gcc is the standard
    compiler under Linux, OS X, and many other systems.
  
  * If you do not have write access to `/tmp`, you should set the environment
    variable `TMPDIR` to the name of some other temporary directory.
  
  * Under HP/UX, the GNU C Compiler (gcc), the GNU Assembler (gas), and GNU Make
    are all *required*.  The vendor-provided compiler, assembler and make tools
    have major problems.
  
  == INSTALLATION INSTRUCTIONS
  