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 would be nice to have a mechanizm to override this value externally, for example by adding a AR/BAZEL_AR environment variable.
Feature requests: what underlying problem are you trying to solve with this feature?
In nixpkgs we build our own toolchain for macOS from open source components. The static library builds rely on ar, and rules_cc hardcode it to be called at /usr/bin/libtool, which does not belong to our toolchain. Our builds are supposed to not rely on Apple SDK, and, in fact, it need not be even installed. We would like to supply our working version of libtool, the same way we specify CC, but apparently there isn't a way to do so.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
macOS
What's the output of bazel info release?
release 3.7.2- (@non-git)
If bazel info release returns "development version" or "(@non-git)", tell us how you built Bazel.
What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
Description of the problem / feature request:
The path to the archive manipulation tool is hardcoded on macOS
rules_cc/cc/private/toolchain/unix_cc_configure.bzl
Line 375 in 081771d
It would be nice to have a mechanizm to override this value externally, for example by adding a
AR
/BAZEL_AR
environment variable.Feature requests: what underlying problem are you trying to solve with this feature?
In nixpkgs we build our own toolchain for macOS from open source components. The static library builds rely on ar, and rules_cc hardcode it to be called at
/usr/bin/libtool
, which does not belong to our toolchain. Our builds are supposed to not rely on Apple SDK, and, in fact, it need not be even installed. We would like to supply our working version of libtool, the same way we specifyCC
, but apparently there isn't a way to do so.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
macOS
What's the output of
bazel info release
?release 3.7.2- (@non-git)
If
bazel info release
returns "development version" or "(@non-git)", tell us how you built Bazel.What version of rules_cc do you use? Can you paste the workspace rule used to fetch rules_cc? What other relevant dependencies does your project have?
Same as tensorflow 2.7.0: 01d4a48
What Bazel options do you use to trigger the issue? What C++ toolchain do you use?
The toolchain is "stdenv" for x86_64-darwin from nixpkgs based on:
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
The text was updated successfully, but these errors were encountered: