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
I'm trying to use link_extra_lib to link against my C++ runtime environment (a cc_library containing my custom libstdc++.so). This works for regular cc_binaries and cc_tests. However, it does not work for shared libraries, i.e. cc_binary with link_shared=True.
Description of the bug:
I'm trying to use
link_extra_lib
to link against my C++ runtime environment (a cc_library containing my custom libstdc++.so). This works for regular cc_binaries and cc_tests. However, it does not work for shared libraries, i.e. cc_binary with link_shared=True.It appears it might be due to this code:
bazel/src/main/starlark/builtins_bzl/common/cc/cc_shared_library.bzl
Line 1107 in 56bf547
It's however unclear why this restriction applies. Could this be clarified/fixed?
Which category does this issue belong to?
C++ Rules
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Ubuntu 24.04
What is the output of
bazel info release
?release 7.4.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD
?If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
No response
Have you found anything relevant by searching the web?
Asked on Slack and got the suggestion to file an issue.
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: