Age | Commit message (Collapse) | Author |
|
If [batch mode is] set, Bazel will be run as just a client process
without a server, instead of in the standard client/server mode. [1]
It is not necessary to shutdown a bazel server in batch mode.
[1] https://docs.bazel.build/versions/master/user-manual.html
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
|
|
Move binary bazel from ${S} to ${WORKDIR}/bazel
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
|
|
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
|
|
1. The problem is the binary is edited after by setting the rpath. Which might
mess up with zip data, you might want to run zip -A on Bazel. It stills needs
to extract the install key to verify it does not need to extract all the
remaining parts. Also Bazel contains other C++ binary and you are going to
run in the rpath problem all the time.
https://github.com/bazelbuild/bazel/issues/2978
2. Since binary bazel in recipe-sysroot-native is a hardlink, while multiple
recipes invoke one bazel at the same time, there is probably a race error
...
FATAL: Failed to open Bazel as a zip file: (error: 5): Input/output error
...
Copy and run a duplicated bazel could workaround it
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
|
|
The build steps refers README of https://github.com/tensorflow/estimator
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
|