tree 206fcc2d9ac4cd461a1816ef4caf96207e6eb46b
parent 4c0770397a31b8d034c3b142d51986797fb89359
author garyschulte <gts.mobile@gmail.com> 1581945877 -0800
committer Copybara-Service <copybara-worker@google.com> 1581945936 -0800

Add aarch64 configuration condition for jni gcc includes

Very light PR which adds arm64 platform rule for building bazel.

When building bazel from sources on linux_aarch64, the build would fail during c++ compilation, complaining about a missing jni platform include:

```
INFO: Analyzed target //src:bazel (1 packages loaded, 194 targets configured).
INFO: Found 1 target...
ERROR: /home/ubuntu/dev/bazel/src/main/java/com/google/devtools/build/lib/syntax/BUILD:150:1: C++ compilation of rule '//src/main/java/com/google/devtools/build/lib/syntax:libcpu_profiler.so' failed (Exit 1) gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 24 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
In file included from src/main/java/com/google/devtools/build/lib/syntax/cpu_profiler_unimpl.cc:17:0:
bazel-out/aarch64-fastbuild/bin/external/bazel_tools/tools/jdk/include/jni.h:45:10: fatal error: jni_md.h: No such file or directory
 #include "jni_md.h"
          ^~~~~~~~~~
compilation terminated.
Target //src:bazel failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 2.737s, Critical Path: 0.73s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
```

After adding aarch64 select, the build is successful.

Closes #10748.

PiperOrigin-RevId: 295567365