Summary: | sci-libs/tensorflow-1.14.0_rc0 - ERROR: .../work/tensorflow-1.14.0-rc0-python3_7/tensorflow/contrib/rpc/python/kernel_tests/BUILD:13:1: ...: Found tool(s) 'bazel-out/host/bin/external/grpc/grpc_python_plugin' in inputs. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
Component: | Current packages | Assignee: | Jason Zaman <perfinion> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Helmut Jarausch
2019-06-19 08:58:20 UTC
(In reply to Helmut Jarausch from comment #0) > Found tool(s) 'bazel-out/host/bin/external/grpc/grpc_python_plugin' in > inputs. > A tool is an input with executable=True set. All tools should be passed > using the 'tools' argument \ > instead of 'inputs' in order to make their runfiles available to the action. > This safety check will not be performed once the action is modified to take > a 'tools' argument. > To temporarily disable this check, set > --incompatible_no_support_tools_in_action_inputs=false. This error message is from Bazel, not Protobuf. Probably you upgraded Bazel recently. Please try building with different versions of Bazel. And try sci-libs/tensorflow-1.14.0 which was added today. Actually in https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9d23ef3049aa6719ec03b3bcadff19d4772d28ee this is seen which matches workaround mentioned in error message: @@ -242,6 +247,7 @@ src_configure() { echo 'build --config=noaws --config=nohdfs --config=noignite --config=nokafka' >> .bazelrc || die echo 'build --define tensorflow_mkldnn_contraction_kernel=0' >> .bazelrc || die + echo 'build --incompatible_no_support_tools_in_action_inputs=false' >> .bazelrc || die } if use python; then python_foreach_impl run_in_build_dir do_configure So the problem should be already fixed in sci-libs/tensorflow-1.14.0. (In reply to Arfrever Frehtes Taifersar Arahesis from comment #2) > And try sci-libs/tensorflow-1.14.0 which was added today. Yes, it's fixed in tensorflow-1.14.0. Thanks, Helmut Is re-opening of this bug your mistake? |