Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-19 09:13:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

README-hacking: update

Browse Source
This commit is contained in:
Akim Demaille
2018-12-28 08:21:53 +01:00
parent f773e6ead5
commit 7c25df547e
1 changed files with 16 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
README-hacking
View File

@@ -91,20 +91,20 @@ might be needed.
** First checkout ** First checkout
Obviously, if you are reading these notes, you did manage to check out Obviously, if you are reading these notes, you did manage to check out this
this package from the repository. For the record, you will find all the package from the repository. For the record, you will find all the relevant
relevant information on: information on:
http://savannah.gnu.org/git/?group=bison http://savannah.gnu.org/git/?group=bison
Bison uses Git submodules: subscriptions to other Git repositories. Bison uses Git submodules: subscriptions to other Git repositories. In
In particular it uses gnulib, the GNU portability library. To ask Git particular it uses gnulib, the GNU portability library. To ask Git to
to perform the first checkout of the submodules, run perform the first checkout of the submodules, run
$ git submodule update --init $ git submodule update --init
The next step is to get other files needed to build, which are The next step is to get other files needed to build, which are extracted
extracted from other source packages: from other source packages:
$ ./bootstrap $ ./bootstrap
@@ -115,14 +115,15 @@ bootstrap.
If it fails with missing symbols (e.g., "error: possibly undefined macro: If it fails with missing symbols (e.g., "error: possibly undefined macro:
AC_PROG_GNU_M4"), you are likely to have forgotten the submodule AC_PROG_GNU_M4"), you are likely to have forgotten the submodule
initialization part. Otherwise, there you are! Just initialization part. To recover from it, run `git reset --hard HEAD`, and
restart with the submodule initialization. Otherwise, there you are! Just
$ ./configure $ ./configure
$ make $ make
$ make check $ make check
At this point, there should be no difference between your local copy, At this point, there should be no difference between your local copy, and
and the master copy: the master copy:
$ git diff $ git diff
@@ -132,9 +133,9 @@ Enjoy!
** Updating ** Updating
The use of submodules make things somewhat different because git does The use of submodules make things somewhat different because git does not
not support recursive operations: submodules must be taken care of support recursive operations: submodules must be taken care of explicitly by
explicitly by the user. the user.
*** Updating Bison *** Updating Bison