  
  [1X2 Installation of the [5Xorb[1X-Package[0X
  
  To  install  this package just extract the package's archive file to the GAP
  [11Xpkg[0m directory.
  
  By  default  the  [5Xorb[0m  package is not automatically loaded by [5XGAP[0m when it is
  installed.  You  must  load  the package with [10XLoadPackage("orb");[0m before its
  functions become available.
  
  As  of version 3.0, the [5Xorb[0m package has a [5XGAP[0m kernel component which must be
  compiled.  This  component  does  not actually contain new functionality but
  will  improve  the  performance  of  AVL trees and hash tables significantly
  since many core routines are implemented in the C language at kernel level.
  
  To compile the C part of the package do (in the [11Xpkg[0m directory)
  
      cd orb
      ./configure [path]
  
  where  "path"  is  a  path  to the main [5XGAP[0m root directory (if not given the
  default "[11X../..[0m" is assumed).
  
  Afterwards call "[11Xmake[0m" to compile a binary file.
  
  If  you  installed  [5XGAP[0m  on  several  architectures,  you  must execute this
  configure/make   step   on  each  of  the  architectures  immediately  after
  configuring [5XGAP[0m itself on this architecture.
  
  If  you  installed  the package in another "[11Xpkg[0m" directory than the standard
  "[11Xpkg[0m" directory in your [5XGAP[0m 4 installation, then you have to add the path to
  the  directory containing your "[11Xpkg[0m" directory to [5XGAP[0m's list of directories.
  This  can be done by starting [5XGAP[0m with the "[11X-l[0m" command line option followed
  by  the  name  of  the  directory  and  a  semicolon. Then your directory is
  prepended  to the list of directories searched. Otherwise the package is not
  found by [5XGAP[0m. Of course, you can add this option to your [5XGAP[0m startup script.
  
  
  [1X2.1 Static linking[0X
  
  This might be interesting for M$ Windows users, as dynamic loading of binary
  modules  does  not  always  work there. You can also create a new statically
  linked "[11Xgap[0m" binary as follows:
  
  Go  into  the main [5XGAP[0m directory and then into [11Xbin/BINDIR[0m. Here [11XBINDIR[0m means
  the  directory  containing  the "[11Xgap[0m" executable after compiling "[11Xgap[0m". This
  directory  also  contains the [5XGAP[0m compiler script "[11Xgac[0m". Assuming [5Xorb[0m in the
  standard location you can then say
  
      ./gac -o gap-static -p "-DORBSTATIC" -P "-static" ../../pkg/orb/src/orb.c
  
  Then  copy your "[11Xgap[0m" start script to, say, "[11Xgaps[0m" and change the references
  to the [5XGAP[0m binary to "[11Xgap-static[0m".
  
  Note  that  you  have  to  replace  [11XBINDIR[0m  by the name containing the "[11Xgap[0m"
  executable  after  compiling GAP as above. If you have installed the package
  in  a  different place than the standard, you have to replace "[11X../..[0m" in the
  above  command  by  the path to the directory containing the "[11Xpkg[0m" directory
  into  which  you installed [5Xorb[0m. If you want to install more than one package
  with  a  C-part  like this package, you can still create a statically linked
  [5XGAP[0m  executable by combining all the compile and link options and all the .c
  files as in the ./gac command above. For the [5Xorb[0m package, you have to add
  
      -DORBSTATIC
  
  to the string of the -p option and the file
  
    ../../pkg/orb/src/orb.c
  
  somewhere  on  the  command  line. As above, "[11X../..[0m" and "[11XBINDIR[0m" have to be
  replaced if you installed in a non-standard location.
  
  
  [1X2.2 Recompiling the documentation[0X
  
  Recompiling  the documentation is possible by the command "[11Xgap makedoc.g[0m" in
  the [11Xorb[0m directory. But this should not be necessary.
  
  Please,  send  us an e-mail if you have any questions, remarks, suggestions,
  etc.  concerning this package. Also, I would like to hear about applications
  of this package.
  
  Jürgen Müller, Max Neunhöffer and Felix Noeske
  
