This change updates the Bazel version used in TensorFlow, JAX, and XLA projects from 7.4.1 to 7.7.0 in `.bazelversion` files and build scripts.
PiperOrigin-RevId: 826075658
- Disabled Bzlmod for now before we start the migration
- Disabled cc toolchain resolution for now
- Fixed transition on `--modify_execution_info` due to https://github.com/bazelbuild/bazel/pull/16262
- Explicitly added `-Wl,-undefined,dynamic_lookup` as linkopt on macOS after https://github.com/bazelbuild/bazel/pull/16414
- Set `-force_no_whole_archive` for host features
- Addressed Windows linking issue by adding `@com_googlesource_code_re2//:__subpackages__` in `exports_filter` of `//tensorflow/python:pywrap_tensorflow_internal`
- Removed `license` attribute on cc_shared_library
- Fixed license checks
PiperOrigin-RevId: 731344894
Testing to see if this fixes issues with cc_shared_library without breaking other builds.
See https://github.com/bazelbuild/bazel/commits/release-5.2.0, 4fd7983ca82fab536b8f9bb589610036b01d7490 is only commit on April 28th and shows as passing CI.
PiperOrigin-RevId: 445708526
Testing to see if this fixes issues with cc_shared_library without breaking other builds.
See https://github.com/bazelbuild/bazel/commits/release-5.2.0, 4fd7983ca82fab536b8f9bb589610036b01d7490 is only commit on April 28th and shows as passing CI.
PiperOrigin-RevId: 445453119
Rolling releases break builds in our ecosystem, so we cannot use them.
See c39f19c52a (commitcomment-72479544)
Windows builds likely broken by switching to rolling release too, so testing.
Switching to rolling release did not solve any of the issues we are seeing with cc_shared_library implementation
PiperOrigin-RevId: 445438661
Since TF is in the progress of migrating to `cc_shared_library`, we are stress testing Bazel and uncovering a large number of bugs. We are in the state where some TF builds are broken with cascading failures and there is a long wait until a new LTS Bazel release. So, we're switching to rolling releases in an attempt to fix the builds.
However, if this causes more failures than it resolves, we will need to return back to stable releases.
PiperOrigin-RevId: 445259819
`.bazelversion` specifies the Bazel version that TensorFlow uses. This changelist updates the Bazel version from 4.2.2 to 5.0.0. It also updates the CI environment.
PiperOrigin-RevId: 424897733
Change-Id: Idd427ee8b1fdc8212211fb22c25989cb47350ab4
Bug fixed: https://github.com/bazelbuild/bazel/issues/3828
We need this because we are working on integrating TF with a different project that should remove the breakages caused by LLVM integration
PiperOrigin-RevId: 348886284
Change-Id: Iad539321f1ba7590e4ee77b93d67eb5401d9fec8
This is necessary to start using bazel's experimental cc_shared_library support.
This change is part of the refactoring described in https://github.com/tensorflow/community/pull/179
PiperOrigin-RevId: 294736824
Change-Id: I8d13c71545cf2f2edd47818b40fa413e3e9c3254
This is necessary to start using bazel's experimental cc_shared_library support.
This change is part of the refactoring described in https://github.com/tensorflow/community/pull/179
PiperOrigin-RevId: 288808507
Change-Id: Ie78fb4ff8dad128ebef280037cce4d3c4f42addc
Follow up of cl/274686963
RELNOTES: If you're building Tensorflow from source, consider using bazelisk (https://github.com/bazelbuild/bazelisk) to automatically download and launch the correct Bazel version. Bazelisk reads the `.bazelversion` file at the root of the project directory.
PiperOrigin-RevId: 274840419
Change-Id: Idae8abf7014b0a593c36068603512545c0f3dfaf
