Skip to content

Fix: local build tools explain a missing dsp_asm and a /private/tmp output - #1292

Merged
npp1993 merged 1 commit into
repeat98:mainfrom
npp1993:claude/fix-local-build-tools
Nov 7, 2026
Merged

npp1993 merged 1 commit into
repeat98:mainfrom
npp1993:claude/fix-local-build-tools

Conversation

@npp1993

@npp1993 npp1993 commented Nov 7, 2026

Copy link
Copy Markdown
Collaborator
  • What was wrong or hard: Two local traps while submitting Improved Envelopes (Analog Rytm MKII: Improved Envelopes 0.1.0-experimental #1291). (1) bash scripts/build-elemod-isolated.sh (and build-modules-isolated.sh) with an output folder under /private/tmp fails on macOS with Docker Desktop: invalid mount config for type "bind": bind source path does not exist, with no hint that an output folder under $HOME works. (2) A local npm run sdk:check (so pr:ready) without dsp_asm fails test_published_module_packages_rebuild_byte_for_byte with FileNotFoundError: 'dsp_asm', even for Rytm-only work: scripts/octatrack-module-packages.py --check skips packages when m68k-elf binutils or the Elekloader checkout are missing, but Analog BD's engine (hook_engines.PACKAGES) also needs dsp_asm and had no such gate.
  • What this changes: The wrapper scripts/octatrack-module-packages.py (not the base-pinned builder) skips an engine-carrying package with a one-line note when no dsp_asm is found (ELEKLOADER_DSP_ASM, PATH, or the npm run upstream:tools octabam build, as base_bound finds it), like its siblings. Both isolated build scripts print "Docker may not share …: choose an output folder under $HOME." when docker run fails on a /private/… output, keeping Docker's exit status. One sentence in docs/DEVELOPER_WORKFLOW.md ("Compiled packages") now says the engine package is skipped without dsp_asm. Changelog entry added.
  • How I checked it: octatrack-module-packages.py --check without dsp_asm: was the FileNotFoundError, now exit 0 with analog-bassdrum needs dsp_asm … and every other package identical; with ELEKLOADER_DSP_ASM set, analog-bassdrum 6272600408466c3e identical, exit 0. python3 -m unittest test_module_packages_cli test_module_packages_abi9 test_runtime_loader…byte_for_byte: OK. build-elemod-isolated.sh . /private/tmp/…/out <modwerk-source-tools id> on Docker Desktop: Docker's error, then the new hint, exit 125. npm run pr:ready: Ready.
  • What the guides lacked or got wrong, and where I fixed it: docs/DEVELOPER_WORKFLOW.md "Compiled packages" said sdk:check "then needs dsp_asm" without saying what happens without it; it now says the engine package is skipped with a note. The Docker trap is caught by the script, so no prose.

🤖 Generated with Claude Code

…utput

`octatrack-module-packages.py --check` (run by sdk:check and pr:ready) now
skips the Analog BD engine package with a note when no dsp_asm is found,
as it skips the others without m68k-elf binutils or Elekloader, instead of
failing with FileNotFoundError. The isolated build scripts print the fix
(an output folder under $HOME) when Docker fails on a /private output.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added the bug Something isn't working label Nov 7, 2026
@npp1993
npp1993 enabled auto-merge (squash) November 7, 2026 05:43
@npp1993
npp1993 merged commit d7e0733 into repeat98:main Nov 7, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant