(AT_COMPILE): Use new LDFLAGS, LIBS vars, to avoid testing problems

[bison.git] / README

diff --git a/README b/README
index ea5f743d43ad8ee8534658e50f9ecfa4485eecd2..5a0526ac02a4c1e5015d5eea72cfe44c3ff6ceef 100644 (file)
--- a/README
+++ b/README
@@ -1,6 +1,7 @@
 This directory contains the Bison parser generator.
 
 See the file INSTALL for compilation and installation instructions.
 This directory contains the Bison parser generator.
 
 See the file INSTALL for compilation and installation instructions.

+See the file doc/FAQ for frequently asked questions.

 
 It was once true that, when installing Bison on Sequent (or Pyramid?)
 systems, you had to be in the Berkeley universe.  This may no longer
 
 It was once true that, when installing Bison on Sequent (or Pyramid?)
 systems, you had to be in the Berkeley universe.  This may no longer


@@ -10,6 +11,14 @@ On VMS, you will probably have to create Makefile from Makefile.in by
 hand.  Remember to do `SET COMMAND BISON' to install the data in
 `BISON.CLD'.
 
 hand.  Remember to do `SET COMMAND BISON' to install the data in
 `BISON.CLD'.
 

-Send bug reports to bug-gnu-utils@prep.ai.mit.edu.  Please include the
-version number from `bison --version', and a complete, self-contained
-test case in each bug report.
+VMS and MS-DOS builds are probably broken right now.  If you are able
+to build Bison on either platform and you need to make changes to do
+so, please submit those changes as a bug report.
+
+Send bug reports to bug-bison@gnu.org.  Please include the version
+number from `bison --version', and a complete, self-contained test
+case in each bug report.
+
+If you have questions about using Bison which the documentation does
+not answer, send mail to help-bison@gnu.org.
+