bazelbuild/bazel

(docu) clarify if openjdk-11 is expected to work

Open

#11,205 opened on Apr 23, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (4,465 forks)batch import
P3help wantedteam-Documentationteam-OSStype: documentation (cleanup)

Repository metrics

Stars
 (25,384 stars)
PR merge metrics
 (Avg merge 22d 20h) (77 merged PRs in 30d)

Description

Description of the problem / feature request:

I'm bootstrapping on ARM/aarch64 because there are no binaries. The Bootstrapping docu claims:

You must install version 8 of the JDK. Versions other than 8 are not supported.

Debian (Buster) has no packages for JDK 8 (for aarch64), so I installed openjdk-11 instead. It seems to work fine.

This would be great to know in advance. The docu implies that my only option is to build JDK8 first, which would be quite an extra step.

It also claims that I need:

EXTRA_BAZEL_ARGS="--host_javabase=@local_jdk//:jdk"

which I've omitted. The build was successful.

What operating system are you running Bazel on?

Linux (aarch64, Debian Buster)

What's the output of bazel info release?

release 3.1.0- (@non-git)

If bazel info release returns "development version" or "(@non-git)", tell us how you built Bazel.

Downloaded the .zip and ran ./compile.sh with no arguments.

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

not a git repository

Contributor guide

Research direction
Test bootstrapping Bazel on ARM/aarch64 with JDK 11 without the recommended extra args. Verify success and update the bootstrapping documentation to clarify that JDK 11 is also supported on ARM and whether the EXTRA BAZEL ARGS flag is necessary.
Tech stack
java
Domain
build system
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80