doc: Remind developers to build Guix.

The previous instructions were correct, but we got too many bug reports
with a root cause of "did not build Guix yet".

Other parts of the manual already instruct `make && make check`, so this
makes the treatment of building Guix more consistent, too.

* doc/contributing.texi (Building from Git): Instruct the user to run
`make` when building Guix.
This commit is contained in:
Leo Famulari 2021-04-04 13:28:46 -04:00
parent b5d7ea6f37
commit 5b97804e87
No known key found for this signature in database
GPG key ID: 2646FA30BACA7F08

View file

@ -126,10 +126,10 @@ Store}, for information about this), usually @file{/var}. Note that you
will probably not run @command{make install} at the end (you don't have will probably not run @command{make install} at the end (you don't have
to) but it's still important to pass the right @code{localstatedir}. to) but it's still important to pass the right @code{localstatedir}.
Finally, you have to invoke @code{make check} to run tests Finally, you have to invoke @code{make && make check} to build Guix and
(@pxref{Running the Test Suite}). If anything run the tests (@pxref{Running the Test Suite}). If anything fails, take
fails, take a look at installation instructions (@pxref{Installation}) a look at installation instructions (@pxref{Installation}) or send a
or send a message to the @email{guix-devel@@gnu.org, mailing list}. message to the @email{guix-devel@@gnu.org, mailing list}.
From there on, you can authenticate all the commits included in your From there on, you can authenticate all the commits included in your
checkout by running: checkout by running: