We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to handle alternatives?
In a minimal example that just depends on f37 binutils:
rpmtree( name = "sandbox", rpms = [ "@binutils-0__2.38-25.fc37.x86_64//rpm", ], visibility = ["//visibility:public"], )
.../usr/bin/ld ends up being the GOLD linker:
/usr/bin/ld
$ .bazeldnf/sandbox/default/root/bin/ld --version GNU gold (version 2.38-25.fc37) 1.16
In the binutils spec, BFD is the default through the alternatives mechanism: https://src.fedoraproject.org/rpms/binutils/blob/f36/f/binutils.spec#_455
A clean Fedora 37 container uses GNU ld by default even though binutils-gold is installed:
$ ld --version GNU ld version 2.38-25.fc37
How can I replicate this using bazeldnf?
The text was updated successfully, but these errors were encountered:
Our current workaround is to simply do it manually:
# Manually resolve alternatives (https://github.com/rmohr/bazeldnf/issues/28) ln -r -s -f "${SANDBOX}/root/usr/bin/ld.bfd" "${SANDBOX}/root/usr/bin/ld"
Sorry, something went wrong.
symlinks can be directly set on the rpmtree target like here: https://github.com/kubevirt/kubevirt/blob/a06915c634a6bc430dac02a8bc8bee048644bdcb/rpm/BUILD.bazel#L1377.
rpmtree
No branches or pull requests
How to handle alternatives?
In a minimal example that just depends on f37 binutils:
...
/usr/bin/ld
ends up being the GOLD linker:In the binutils spec, BFD is the default through the alternatives mechanism: https://src.fedoraproject.org/rpms/binutils/blob/f36/f/binutils.spec#_455
A clean Fedora 37 container uses GNU ld by default even though binutils-gold is installed:
How can I replicate this using bazeldnf?
The text was updated successfully, but these errors were encountered: