diff options
| author | Akim Demaille <akim@lrde.epita.fr> | 2012-10-26 16:50:26 +0200 |
|---|---|---|
| committer | Akim Demaille <akim@lrde.epita.fr> | 2012-10-26 16:58:55 +0200 |
| commit | d0a304384f4207bdf7f8b1038c2226c312f5e954 (patch) | |
| tree | 1362b308c1b3ae17301c56f53e62fdca13e5e1a7 /README-hacking | |
| parent | 6b1cbda1b9e0e8f29c0a6e4e44ce2d5a2aee974f (diff) | |
| parent | 71cb558dfe0f9c80e697308a5084de3b9926ee9c (diff) | |
| download | bison-d0a304384f4207bdf7f8b1038c2226c312f5e954.tar.gz | |
Merge remote-tracking branch 'origin/maint'
* origin/maint: (46 commits)
doc: minor style change
maint: use gendocs's new -I option
regen
yacc.c: do not define location support when not using locations
maint: be compilable with GCC 4.0
tests: address a warning from GCC 4.4
tests: don't use options that Clang does not support
tests: restore the tests on -Werror
regen
parse-gram: update the Bison interface
fix comment
maint: post-release administrivia
version 2.6.4
regen
2.6.4: botched 2.6.3
maint: post-release administrivia
version 2.6.3
gnulib: update
tests: check %no-lines
NEWS: warnings with clang
...
Conflicts:
NEWS
TODO
data/c.m4
data/java.m4
doc/Makefile.am
src/getargs.c
src/getargs.h
src/output.c
src/parse-gram.c
src/parse-gram.h
src/parse-gram.y
src/reader.h
Diffstat (limited to 'README-hacking')
| -rw-r--r-- | README-hacking | 25 |
1 files changed, 13 insertions, 12 deletions
diff --git a/README-hacking b/README-hacking index ff5b4345..71680100 100644 --- a/README-hacking +++ b/README-hacking @@ -50,16 +50,17 @@ These requirements do not apply when building from a distribution tarball. ** Requirements -We've opted to keep only the highest-level sources in the repository. -This eases our maintenance burden, (fewer merges etc.), but imposes more +We've opted to keep only the highest-level sources in the repository. This +eases our maintenance burden, (fewer merges etc.), but imposes more requirements on anyone wishing to build from the just-checked-out sources. For example, you have to use the latest stable versions of the maintainer tools we depend upon, including: -- Automake <http://www.gnu.org/software/automake/> - Autoconf <http://www.gnu.org/software/autoconf/> +- Automake <http://www.gnu.org/software/automake/> - Flex <http://www.gnu.org/software/flex/> - Gettext <http://www.gnu.org/software/gettext/> +- Graphviz <http://www.graphviz.org> - Gzip <http://www.gnu.org/software/gzip/> - Perl <http://www.cpan.org/> - Rsync <http://samba.anu.edu.au/rsync/> @@ -68,16 +69,16 @@ tools we depend upon, including: Valgrind <http://valgrind.org/> is also highly recommended, if it supports your architecture. -Bison is written using Bison grammars, so there are bootstrapping -issues. The bootstrap script attempts to discover when the C code -generated from the grammars is out of date, and to bootstrap with an -out-of-date version of the C code, but the process is not foolproof. -Also, you may run into similar problems yourself if you modify Bison. +Bison is written using Bison grammars, so there are bootstrapping issues. +The bootstrap script attempts to discover when the C code generated from the +grammars is out of date, and to bootstrap with an out-of-date version of the +C code, but the process is not foolproof. Also, you may run into similar +problems yourself if you modify Bison. -Only building the initial full source tree will be a bit painful. -Later, after synchronizing from the repository a plain 'make' should -be sufficient. Note, however, that when gnulib is updated, running -'./bootstrap' again might be needed. +Only building the initial full source tree will be a bit painful. Later, +after synchronizing from the repository a plain 'make' should be sufficient. +Note, however, that when gnulib is updated, running './bootstrap' again +might be needed. ** First checkout |