Skip to content

penguin: fix compiled env module build in CI#8

Merged
lacraig2 merged 1 commit into
mainfrom
fix/env-module-build
Jun 11, 2026
Merged

penguin: fix compiled env module build in CI#8
lacraig2 merged 1 commit into
mainfrom
fix/env-module-build

Conversation

@lacraig2

Copy link
Copy Markdown
Contributor

Summary

v0.0.8 shipped without any compiled CPUArchState CFFI modules (lib/penguin-qemu-env/ is absent from the package and no manifest entry has an env_module key): ffi.compile() needs Python.h, the builder image lacks python3-dev (build-essential does not provide it), and penguin-env-cffi-gen.py's per-target fallback quietly shipped the ABI headers only — which is why the release still succeeded.

Two changes:

  • Install python3-dev in the builder image.
  • Add lib/penguin-qemu-env/ to the release artifact verification in publish.yml, so a silent header-only fallback can never publish again.

No penguin-side change needed once the next release ships: the compat shim already prefers compiled modules via the manifest and currently falls back to the ABI headers (verified working against the v0.0.8 artifact).

Follow-up to #7.

The v0.0.8 release shipped without any compiled CPUArchState CFFI
modules: ffi.compile() needs Python.h, the builder image lacks
python3-dev, and penguin-env-cffi-gen.py's per-target fallback quietly
shipped ABI headers only. Install python3-dev and gate the release on
lib/penguin-qemu-env/ being present in the package so a silent
fallback cannot publish again.
@lacraig2 lacraig2 merged commit a92ffba into main Jun 11, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant