aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/versions/master/docs
diff options
context:
space:
mode:
authorGravatar Klaus Aehlig <aehlig@google.com>2017-03-02 10:25:33 +0000
committerGravatar Yue Gan <yueg@google.com>2017-03-02 13:32:31 +0000
commita763ce111a311cb4653edb3d202b2382aa8074ef (patch)
tree074ae15de5468d7a3a5f64b7bf45fc1930f4a569 /site/versions/master/docs
parent508af301b3d7c1465189a0edfe4707a1c261a658 (diff)
Update instructions for building bazel from source
As we do not recommend using versions of bazel pre 0.4.1, drop instructions on how to build those old versions. Also, emphasize that building bazel at HEAD is only assumed to work, if the latest version of bazel is used. Hopefully, this will help avoid misunderstandings as in #2608. -- Change-Id: I5192bbc7420a3611fad99b8872e0074a02060183 Reviewed-on: https://cr.bazel.build/9119 PiperOrigin-RevId: 148982493 MOS_MIGRATED_REVID=148982493
Diffstat (limited to 'site/versions/master/docs')
-rw-r--r--site/versions/master/docs/install.md5
1 files changed, 1 insertions, 4 deletions
diff --git a/site/versions/master/docs/install.md b/site/versions/master/docs/install.md
index e67c7247a3..87244c5f56 100644
--- a/site/versions/master/docs/install.md
+++ b/site/versions/master/docs/install.md
@@ -273,10 +273,7 @@ The standard way of compiling a release version of Bazel from source
is to use a distribution archive. Download `bazel-<VERSION>-dist.zip`
from
the [release page](https://github.com/bazelbuild/bazel/releases) for
-the desired version (for releases 0.4.0 and earlier: download the "source
-code" zip archive and note that it will only work for the supported
-architectures as it contains binaries). We recommend to also verify
-the signature made by our
+the desired version. We recommend to also verify the signature made by our
[release key](https://bazel.build/bazel-release.pub.gpg) 48457EE0.
Unzip the archive and call `bash ./compile.sh`; this will create a