2 Commits

Include renames

Author	SHA1	Message	Date
Oleksandr ShyshatskyiandClaude Opus 5	6a750f6bcc	Moonraker serves on the 3.13 we built, with nothing from /usr/prog ... The previous commit proved every component IMPORTS. Importing is not serving, so this runs it. case-moonraker313.sh starts Moonraker on the exact command line payload/etc/s6/moonraker/run execs -- only with our interpreter -- against the mod's own assets/moonraker.conf, and asks the printer what happened: * bound :7125 in 3s, with /proc/PID/cmdline confirming our interpreter and our entry point rather than a coincidence * GET /server/info answers 200 with 23 components loaded and none failed. /machine/system_info, a different component reading this box's own /proc, reports cpu: mips and python 3.13.7 [GCC 7.2.0] * the database really works, which is the entire reason for the exercise: a POST wrote a namespace, a GET read it back, the namespace appears beside Moonraker's own, and data.mdb is 147456 bytes on disk -- through lmdb's CPython extension, not the compile-at-import cffi fallback that would try to invoke a compiler this printer does not have * still alive and still answering 120 seconds later, with no tracebacks in its log, and SIGTERM released the port in 2s * the RUNNING process maps zero libraries under /usr/prog, with LD_LIBRARY_PATH completely unset -- not merely purged of /usr/prog * negative controls: nothing on :7125 beforehand, and with site-packages moved aside it never binds at all libsodium was the last /usr/prog string in the picture and is now ours. libsodium 1.0.20, cross-built with the Ingenic toolchain in 24 seconds, gated at 0x70001407 nan2008/o32/mips32r2, needing only libpthread, libc and the loader, 406KB stripped into $MODDIR/lib. It computes rather than merely loading: sodium_version_string is 1.0.20, its BLAKE2b-256 matches CPython's own _blake2 on the same kernel, and libnacl.sign.Signer/Verifier -- the exact ed25519 pair authorization.py imports -- signs, verifies, and rejects a tampered message. It costs anvil-env.sh nothing, which was not obvious and had to be measured. libnacl's third fallback builds a path out of its own __file__, so from $MODDIR/lib/python3.13/site-packages/libnacl it resolves $MODDIR/lib/libsodium.so by absolute path -- working with LD_LIBRARY_PATH unset entirely. Recorded in the README, because it works only because the prefix happens to contain the string "lib": a prefix without it would break this silently. klippy was scanned rather than guessed at. Its module-scope third-party imports are cffi, greenlet, jinja2, pyserial and numpy; four of the five are built and proven, and cffi already dlopens the printer's real c_helper.so. numpy is at module scope only in extras/stepper_resonance_tester.py, which Klipper loads on demand, and it is a multi-day problem that costs input-shaper calibration rather than printing. There is no removed-stdlib usage anywhere in klippy -- no imp, distutils, asyncore, cgi or getargspec. What is left is packaging, not capability, and the README says so in order. The sharp one: section 5c's trim deletes include/ and config-3.13-*, which the package build needs, so the package build has to run inside 5c against the untrimmed stage. And the ABI gate walks the build cache rather than the payload, so anything staged straight into $MOD_PAYLOAD would bypass it -- coverage, not logic. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-27 10:41:24 +03:00
Oleksandr ShyshatskyiandClaude Opus 5	da65764b86	Moonraker's whole component set imports on the 3.13 we built ... Nineteen packages cross-built for mipsel, twelve of them C extensions, every one gated at nan2008/o32/mips32r2. Not wired into bin/patch.sh yet -- this preserves the build and, more importantly, what it cost, the way tools/supervisor/ does for s6. The measurement lives in test/integration/printer/case-pyext.sh rather than in a paragraph. Two results carry the phase. The first: 3.13's cffi dlopens the printer's OWN /usr/prog/klipper/klippy/chelper/c_helper.so, resolves stepcompress_alloc, steppersync_alloc and itersolve_generate_steps, and calls one. That is phase 7's central question -- whether an interpreter we built can drive FlashForge's C helper -- answered by doing it, and it is the whole reason the interpreter had to be glibc rather than musl. The second: all 16 Moonraker components import on 3.13, with the list taken from CORE_COMPONENTS plus moonraker.conf rather than written down. The negative control is that moving the tree aside fails every third-party import and the database component. The package list is deliberately NOT moonraker-requirements.txt, which installs every optional component's dependencies. It is the closure of what the ENABLED set imports plus klippy's, so no apprise, ldap3, paho-mqtt or zeroconf. msgspec and uvloop are skipped on purpose: Moonraker guards both with contextlib.suppress(ImportError) and falls back to the stdlib. greenlet was the expected blocker and blocked for an unexpected reason. Its MIPS stack-switching assembly was never a problem; greenlet 3.x is C++ and writes its PyTypeObjects as designated initializers, which gcc 7.2 takes only in declaration order with no gaps. The exact rule was probed rather than guessed -- in-order contiguous fine, a trailing gap fine, an interior or leading gap refused -- and fill-designators.py writes the skipped fields back as explicit zeros, reading field order from the target's own headers and refusing to guess when a designator is not in them. Semantically a no-op: static storage duration, those fields were already zero. It switches out and back, in order, on the printer. Three traps worth having in the log. pip silently downloaded x86-64 manylinux wheels for cffi, greenlet and tornado on the first run -- three wrong-architecture .so files sailed through the build and only the ABI gate caught them, so --no-binary :all: is mandatory here rather than cautious. lmdb chose its cffi backend and produced a py3-none-any wheel with mdb.c inside, which is phase 6's recorded trap rebuilt from scratch: on the printer that path invokes a compiler that does not exist. And pillow 10.3.0 cannot be built by any 3.13, cross or not, because its setup.py execs and then reads locals()["__version__"], which PEP 667 broke. One dependency is unsolved and named rather than buried: libnacl ctypes-loads libsodium, which exists on this box only at /usr/prog/libsodium/lib. Measured both ways. So the authorization component keeps the last /usr/prog string in the picture until libsodium is cross-built or that one path entry is kept. What is left before FF_PYTHON could switch is written down in the README, and the honest remaining unknown is at the top of it: every component imports and the entry point loads, but importing is not serving. Nothing has bound :7125 on 3.13 yet. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-27 10:14:38 +03:00