about summary refs log tree commit diff
path: root/compiler/rustc_mir_transform/src/coverage/query.rs
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2023-10-29 12:34:59 +0100
committerGitHub <noreply@github.com>2023-10-29 12:34:59 +0100
commite9c7ebe2cd27c407f04a9ba757fd301f0a3ea3a1 (patch)
tree8af187b54fcf5f80b29f4974242680ae5d6b3c1c /compiler/rustc_mir_transform/src/coverage/query.rs
parentbbcc1691a4646a6d2ebb2189bdff5b878407fbe6 (diff)
parent7a504cc68a56bfaa7855016c81ced9e6b1320fc5 (diff)
downloadrust-e9c7ebe2cd27c407f04a9ba757fd301f0a3ea3a1.tar.gz
rust-e9c7ebe2cd27c407f04a9ba757fd301f0a3ea3a1.zip
Rollup merge of #115968 - git-bruh:master, r=workingjubilee
Don't use LFS64 symbols on musl

Supersedes #106246

~~Note to packagers: If your distro's musl package has already been updated, then you won't be able to build a newer version of rust until a new rust release is made with these changes merged (which can be used to bootstrap). I'm using a super hacky method to bypass this by creating a stub library with LFS64 symbols and building a patched rust, so the symbols satisfy the build requirements while the final compiler build has no references to LFS64 symbols, example: https://codeberg.org/kiss-community/repo/pulls/160/files~~ Doesn't seem to be necessary with new rustup nightly builds, likely due to updates to vendored crates

cc ```@alyssais```
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/query.rs')
0 files changed, 0 insertions, 0 deletions