Android extras build drops JSH_EMBED_PASSPHRASE_FILE when invoking nested make #76

Open
opened 2026-09-12 01:47:57 -04:00 by ober · 0 comments
Owner

During Termux all-features Android builds launched with:

JSH_EMBED=$HOME/.embed JSH_EMBED_ENCRYPT=1 JSH_EMBED_PASSPHRASE_FILE=<temp-file> make android

process snapshots for the nested extras make showed:

JSH_EMBED=/data/data/com.termux/files/home/.embed JSH_EMBED_PASSPHRASE_FILE= EXTRAS_OUTPUT=...

That suggests the passphrase file is not propagated into the nested vendor/jerboa-shell-extras build, even when encryption is requested.

Expected: JSH_EMBED_PASSPHRASE_FILE should be preserved or the build should fail loudly when JSH_EMBED_ENCRYPT=1 has no passphrase.
Actual: nested make appears to receive an empty passphrase file variable, making it unclear whether embed encryption used the requested password.

During Termux all-features Android builds launched with: ``` JSH_EMBED=$HOME/.embed JSH_EMBED_ENCRYPT=1 JSH_EMBED_PASSPHRASE_FILE=<temp-file> make android ``` process snapshots for the nested extras make showed: ``` JSH_EMBED=/data/data/com.termux/files/home/.embed JSH_EMBED_PASSPHRASE_FILE= EXTRAS_OUTPUT=... ``` That suggests the passphrase file is not propagated into the nested `vendor/jerboa-shell-extras` build, even when encryption is requested. Expected: `JSH_EMBED_PASSPHRASE_FILE` should be preserved or the build should fail loudly when `JSH_EMBED_ENCRYPT=1` has no passphrase. Actual: nested make appears to receive an empty passphrase file variable, making it unclear whether embed encryption used the requested password.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ober/jerboa-shell#76
No description provided.