README 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455
  1. This directory contains the Bison parser generator.
  2. To compile it on Unix-like systems:
  3. 1. Type `./configure'. This shell script attempts to guess correct
  4. values for various system-dependent variables used during compilation,
  5. and creates the file `Makefile'. This takes half a minute or so.
  6. If you want to compile in a different directory from the one
  7. containing the source code, `cd' to that directory and run `configure'
  8. with the option `+srcdir=DIR', where DIR is the directory that
  9. contains the source code. The object files and executables will be
  10. put in the current directory. This option only works with versions of
  11. `make' that support the VPATH variable. `configure' ignores any other
  12. arguments you give it.
  13. If your system requires unusual options for compilation or linking
  14. that `configure' doesn't know about, you can give `configure' initial
  15. values for variables by setting them in the environment; in
  16. Bourne-compatible shells, you can do that on the command line like
  17. this:
  18. $ CC='gcc -traditional' LIBS=-lposix ./configure
  19. 2. If you want to change the directories where Bison or its parsers
  20. or documentation will be installed, or the optimization options, edit
  21. `Makefile' and change those values. If you have an unusual system
  22. that needs special compilation options that `configure' doesn't know
  23. about, and you didn't pass them in the environment when running
  24. `configure', you should add them to `Makefile' now. Alternately,
  25. teach `configure' how to figure out that it is being run on a system
  26. where they are needed, and mail the diffs to the address listed at the
  27. end of this file so we can include them in the next release.
  28. 3. Type `make'.
  29. 4. If the program compiles successfully, type `make install' to
  30. install it and its parsers and documentation.
  31. 5. After you have installed the program, you can remove the binary
  32. from the source directory by typing `make clean'. Type `make
  33. distclean' if you also want to remove `Makefile', for instance if you
  34. are going to recompile Bison next on another type of machine.
  35. It was once true that, when installing Bison on Sequent (or Pyramid?)
  36. systems, you had to be in the Berkeley universe. This may no longer
  37. be true; we have no way to tell.
  38. On VMS, you will probably have to create Makefile from Makefile.in by
  39. hand. Remember to do `SET COMMAND BISON' to install the data in
  40. `BISON.CLD'.
  41. Send bug reports to bug-gnu-utils@prep.ai.mit.edu. Please include the
  42. version number from `bison +version', and a complete, self-contained
  43. test case in each bug report.