This package contains the GNU Bison parser generator.

* Installation
** Build
See the file INSTALL for generic compilation and installation
instructions.

Bison requires GNU m4 1.4.6 or later.  See:

      ftp://ftp.gnu.org/gnu/m4/m4-1.4.6.tar.gz

** Internationalization
Bison supports two catalogues: one for Bison itself (i.e., for the
maintainer-side parser generation), and one for the generated parsers
(i.e., for the user-side parser execution).  The requirements between
both differ: bison needs ngettext, the generated parsers do not.  To
simplify the build system, neither are installed if ngettext is not
supported, even if generated parsers could have been localized.  See
http://lists.gnu.org/archive/html/bug-bison/2009-08/msg00006.html for
more details.

* Questions
See the section FAQ in the documentation (doc/bison.info) for
frequently asked questions.  The documentation is also available in
PDF and HTML, provided you have a recent version of Texinfo installed:
run "make pdf" or "make html".

If you have questions about using Bison and the documentation does
not answer them, please send mail to <help-bison@gnu.org>.

* Bug reports
Please 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.

* Copyright statements
For any copyright year range specified as YYYY-ZZZZ in this package,
note that the range specifies every single year in that closed interval.


Local Variables:
mode: outline
End:

-----

Copyright (C) 1992, 1998-1999, 2003-2005, 2008-2012 Free Software
Foundation, Inc.

This file is part of Bison, the GNU Compiler Compiler.

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <http://www.gnu.org/licenses/>.

Here are most of the steps we (maintainers) follow when making a release.

* Start from a clean, up-to-date git directory on "master":

    make -k maintainer-clean || { ./configure && make maintainer-clean; }
    git checkout master
    git pull origin master

* Ensure that the latest stable versions of autoconf, automake, etc.
  are in your PATH.  See the buildreq list in bootstrap.conf for
  the complete list of tools.

* Ensure that you have no uncommitted diffs.  This should produce no
  output:

    git diff

* Ensure that you've pushed all changes that belong in the release:

    git push origin master

* Check that the NixOS/Hydra autobuilder is reporting all is well:

    http://hydra.nixos.org/jobset/gnu/bison-master

* Run the following command to download any new translations:

    ./bootstrap && ./configure

* Pre-release testing: ensure that the following command succeeds:

    make check syntax-check distcheck

* To (i) set the date, version number, and release TYPE on line 3 of
  NEWS, (ii) commit that, and (iii) tag the release, run

    # "TYPE" must be stable, beta or alpha
    make release-commit RELEASE='X.Y TYPE'

* Run the following to create release tarballs.  Your choice selects the
  corresponding upload-to destination in the emitted gnupload command.
  The different destinations are specified in cfg.mk.  See the definitions
  of gnu_ftp_host-{alpha,beta,stable}.

    make release RELEASE='X.Y TYPE'

* Test the tarball.  Copy it to a few odd-ball systems and ensure that
  it builds and passes all tests.

* While that's happening, write the release announcement that you will
  soon post.  Start with the template, $HOME/announce-bison-X.Y
  that was just created by that "make" command.

Once all the builds and tests have passed,

* Run the gnupload command that was suggested by your "make release"
  run above, or run

    make upload RELEASE='X.Y TYPE'

* Wait a few minutes (maybe up to 30?) and then use the release URLs to
  download all tarball/signature pairs and use gpg --verify to ensure
  that they're all valid.

* Push the NEWS-updating changes and the new tag:

    v=$(cat .prev-version)
    git push origin master tag v$v

* Announce it on Savannah first, so you can include the savannah.org
  announcement link in the email message.

  Go to the news-submission form:

    https://savannah.gnu.org/news/submit.php?group=bison

  If it does not work, then enable "News" for the project via this link:

    https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=bison

  Write something like the following:

    Subject: bison-X.Y released [stable]
    +verbatim+
    ...paste the announcement here...
    -verbatim-

  Then go here to approve it:

    https://savannah.gnu.org/news/approve.php?group=bison

* Send the announcement email message.

* After each non-alpha release, run

    make web-manual-update

  to update the on-line manual accessible at

    http://www.gnu.org/software/bison/manual/

The source code of bison 2.7 was downloaded from http://ftp.gnu.org/gnu/bison/.

To build it with the Android build system, we added 2 subdirectories darwin-lib
and linux-lib, as well as an Android.mk.
We used the following steps to generate the Android.mk:
1) On a Mac OS X machine, run ./configure and make, you'll get a list of
generated header files from the log. Copy them to darwin-lib; You can also get
a list of source files from the log. Add them to LOCAL_SRC_FILES in the
Android.mk.
2) Do the same thing on a Linux machine.
3) Comment out the PKGINCLUDEDIR line in darwin-lib/configmake.h and
linux-lib/configmake.h, because we'll pass in the macro from the build system.
4) Define libbison and bison in the Android.mk.