diff options
| author | Alan Somers <asomers@FreeBSD.org> | 2026-09-18 23:06:47 +0000 |
|---|---|---|
| committer | Alan Somers <asomers@FreeBSD.org> | 2026-10-07 17:28:37 +0000 |
| commit | 396c15930651bd7f479929c3f6248b0791665887 (patch) | |
| tree | ee1693c2e9f44d3091aaf06e0d31b1d7d74b1a5a /devel/py-python-json-logger/(public-mirror) | |
| parent | 63eabd479b2b72891deee1d9597d796f8cef4fd1 (diff) | |
RISCV does not include COMPAT11 by default. But Rust's libc bound the
compat-11 symbols until version 0.2.176. Patch a great many Rust ports
to use a newer version of libc, to eliminate the dependency on COMPAT11.
Explicitly patching Cargo.lock isn't usually necessarily, since within
the build jail cargo is forced to use whichever crates Makefile.crates
installs there.
Notes on specific ports:
* textproc/bookokrat: Rework bookokrat's existing patch to be more
robust. Also, report the issue upstream:
https://github.com/bugzmanov/bookokrat/issues/182
* security/sequoia-chameleon-gnupg security/sequoia-sq
"cargo update -p libc" insisted on updating some other crates, too.
* devel/cargo-generate finance/tickrs net-im/gurk-rs
net-p2p/oura textproc/mdbook-linkcheck www/lychee
These creates contained an extra entry in CARGO_CRATES for
openssl-src. I don't know why. Remove it.
* www/tuifeed
Alone among all the crates touched, this one uses cargo's
--locked argument. So I had to create a patch-Cargo.lock file
for it.
There are several other ports that still use old versions of libc. But
for various reasons, each needs more attention that I can afford in this
already-large commit.
PR: 297814
exp-run: antoine
Approved by: portmgr timeout (2+ weeks)
Diffstat (limited to 'devel/py-python-json-logger/(public-mirror)')
0 files changed, 0 insertions, 0 deletions
