You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that bazel-watcher will start breaking with the next Bazel release 0.25 because of an incompatible change (bazelbuild/bazel#7036)
It looks like Tensorflow is still using the legacy 'cc' provider for some Starlark rules. I explained in the issue about the steps you can take to migrate to using CcInfo. The same functionality is available with that new provider.
Here's the error:
ERROR: tensorflow/tensorflow/lite/python/optimize/BUILD:28:1: in deps attribute of _py_wrap_cc rule //tensorflow/lite/python/optimize:tensorflow_lite_wrap_calibration_wrapper_py_wrap: '//tensorflow/lite/python/optimize:calibration_wrapper_lib' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'tf_py_wrap_cc', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1743:16
Analyzing [0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 15887 targets configured)
ERROR: tensorflow/tensorflow/lite/python/optimize/BUILD:28:1: in deps attribute of _py_wrap_cc rule //tensorflow/lite/python/optimize:tensorflow_lite_wrap_calibration_wrapper_py_wrap: '@local_config_python//:python_headers' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'tf_py_wrap_cc', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1743:16
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 15894 targets configured)
ERROR: tensorflow/tensorflow/core/BUILD:2731:1: in deps attribute of _transitive_hdrs rule //tensorflow/core:framework_internal_headers_lib_gather: '//tensorflow/core:lib' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'cc_header_only_library', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1505:54
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 18659 targets configured)
ERROR: tensorflow/tensorflow/core/BUILD:2731:1: in deps attribute of _transitive_hdrs rule //tensorflow/core:framework_internal_headers_lib_gather: '//tensorflow/core:lib_internal' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'cc_header_only_library', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1505:54
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 18662 targets configured)
ERROR: tensorflow/tensorflow/core/BUILD:2731:1: in deps attribute of _transitive_hdrs rule //tensorflow/core:framework_internal_headers_lib_gather: '//tensorflow/core:version_lib' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'cc_header_only_library', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1505:54
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 18665 targets configured)
ERROR: [0mtensorflow/tensorflow/core/BUILD:2731:1: in deps attribute of _transitive_hdrs rule //tensorflow/core:framework_internal_headers_lib_gather: '//tensorflow/core:framework_bounds_check' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'cc_header_only_library', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1505:54
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 18666 targets configured)
ERROR: [0mtensorflow/tensorflow/core/BUILD:2731:1: in deps attribute of _transitive_hdrs rule //tensorflow/core:framework_internal_headers_lib_gather: '//tensorflow/core/platform/default/build_config:platformlib' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'cc_header_only_library', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1505:54
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages\
loaded, 18669 targets configured)
ERROR: [0mtensorflow/tensorflow/core/BUILD:2842:1: in deps attribute of _transitive_hdrs rule //tensorflow/core:stream_executor_headers_lib_gather: '//tensorflow/core:stream_executor' does not have mandatory providers: 'cc'. Since this rule was created by the macro 'cc_header_only_library', the error might have been caused by the macro implementation in tensorflow/tensorflow/tensorflow.bzl:1505:54
Analyzing:[0m target //tensorflow/tools/pip_package:build_pip_package (0 packages
The text was updated successfully, but these errors were encountered:
It seems that bazel-watcher will start breaking with the next Bazel release 0.25 because of an incompatible change (bazelbuild/bazel#7036)
It looks like Tensorflow is still using the legacy 'cc' provider for some Starlark rules. I explained in the issue about the steps you can take to migrate to using CcInfo. The same functionality is available with that new provider.
Here's the error:
The text was updated successfully, but these errors were encountered: