Android boot embedding should not compile large boot files as C byte arrays #74
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?
The Android/Termux all-features build originally generated huge C byte-array headers for boot data, producing a very large C translation unit. On-device clang compilation was memory-heavy enough to destabilize the Termux SSH session during the build.
Local workaround: keep the small generated program header as C, but embed petite/scheme/jsh boot files via an assembler
.incbinobject and reference start/end symbols fromstatic_boot.c. This reduced the generated C header to about 320 KB and allowed repeated builds to finish.Expected: Android build should use
.incbin, objcopy, or another binary-object embedding strategy for large boot images.Actual: C byte-array boot embedding is fragile on Termux/aarch64.