Skip to content

Update ldk-node and bpi#42

Merged
amackillop merged 2 commits into
mainfrom
austin_update-ldk-revs
May 27, 2026
Merged

Update ldk-node and bpi#42
amackillop merged 2 commits into
mainfrom
austin_update-ldk-revs

Conversation

@amackillop

Copy link
Copy Markdown
Contributor

ldk-node rev is moved to the revision from the main branch. bitcoin-payment-instructions updated to match the transient dependency

The new bpi rev pulled reqwest 0.13, whose `rustls` feature forces
aws-lc-rs as the rustls crypto provider via cargo feature unification.
aws-lc-sys then has to cross-compile its bundled C, which conflicts with
the napi-rs docker images on the two gnu Linux targets:

- x86_64-unknown-linux-gnu: aws-lc-sys passes `-fuse-ld=lld` to the
  compiler unconditionally. The image's custom `x86_64-unknown-linux-gnu-gcc`
  does not recognize the flag, but the image's clang (already CC=clang)
  does once lld is installed.
- aarch64-unknown-linux-gnu: the image's custom cross toolchain at
  /usr/aarch64-unknown-linux-gnu has a sysroot missing stdatomic.h.
  Debian's gcc-aarch64-linux-gnu plus libc6-dev-arm64-cross provides
  the C11 atomics header.

The catch is that aws-lc-sys reads TARGET_CC ahead of CC_<target> and
CC. The image pre-sets TARGET_CC to its custom gcc, so any CC_<target>
exports were ignored until we unset TARGET_CC (and TARGET_CXX,
TARGET_AR) first. Same story for CFLAGS on aarch64, which the image
pre-sets to the broken sysroot.

The alternative was patching bpi to use reqwest's `rustls-no-provider`
plus an explicit ring provider, which would have required a runtime
CryptoProvider::install_default() call and another upstream fork bump.
Keeping rustls's default provider was preferred since the CI fix is
self-contained.

Musl targets were not failing in the latest run. If they break later
the same TARGET_CC unset trick should apply.
@amackillop amackillop force-pushed the austin_update-ldk-revs branch from 601ac11 to 0c3ccd9 Compare May 27, 2026 14:15
@amackillop amackillop merged commit 2d9803c into main May 27, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant