Android all-features boot image omits packaged stdlib and vendor modules #72
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
While building all-features jsh on Termux/aarch64, the binary linked successfully but failed at startup with successive missing-library errors:
(std text base64) not found(std net socks5-server) not found(jsh rsync) not found(jdrive s3 config) not found(std os secure-output) not found(std os file-info) not found(std misc channel) not foundThe modules had been compiled under the packaged Jerboa libdir or vendored feature libdirs, but
build-jsh-android.ssdid not include them in the boot image lists. Local workaround was to add packaged stdlib entries plus all-feature jsh modules and vendor modules from jerboa-drive, jerboa-top, and jerboa-rsync to the boot list.Expected: an all-features Android build should produce a self-contained boot image that starts without missing library errors.
Actual: successful link, then runtime import failures.