| commit | 164ffa56dfc68151ec7f33701c304fb86a7bebda | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Tue Aug 27 05:28:31 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 27 05:31:46 2024 -0700 |
| tree | 868fd74637011c1c125ddb858a6442474fd43507 | |
| parent | 4a80a188a5631e1a958917d9104a2120965308a3 [diff] |
Do not wrap object files in `--start-lib/--end-lib` for nodeps libraries When linking a nodeps dynamic library that contains object files produced from tree artifact sources, the library may not contain any references to the symbols in those files. In this case, when wrapping the files in `--start-lib/--end-lib`, they may end up being dropped by the linker, which results in missing symbols compared to a build with `--dynamic_mode=off`. This is fixed by not wrapping object files into `--start-lib/--end-lib` for the nodeps dynamic library link action. Fixes bazelbuild/rules_cc#230 Closes #23084. PiperOrigin-RevId: 667945814 Change-Id: Iec148ad1b86626bb5263fecc9b98b0db89f81ad6
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
