[FEATURE] Assemble original C++ runtime sources through runtime build retirement #616

Open
opened 2026-11-08 18:05:14 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

The admitted C++ archives and runtime-first graph declarations do not yet supply a live source assembly or executable runtime recipe. A verifier's JSON cannot carry original file custody into a compiler invocation.

Proposed behavior and scope

Extend the existing toolchain source feature with an original bounded runtime operation. Retain the exact catalog, runtime policy, Rust source and matching libc++/libc++abi archive receivers through fresh source assembly and runtime effects. Preserve the Rust fork's compiler-rt, libunwind, CMake and runtimes sources. Add only the two explicitly selected missing project trees in an external output namespace; never overwrite the Rust source.

Bind configure/build/install steps to explicitly admitted compiler, CMake/Ninja, target configuration, EriX sysroot and port products. Keep static/shared deployment explicit and fail before upstream execution when required inputs are unresolved. Retain localization, wide characters, Unicode, threads, filesystem, exceptions and RTTI. Compilation and guest rebuilding remain acceptance gates rather than source-control results.

Authority, security and reliability

Register actual input/output receivers before effects. Source digests, paths and recipe records remain data, never owners. Use held descriptors and current original byte/namespace checks at assembly and native admission/settlement; hold all source, tool and product inputs until actual native retirement. No serialized receipt adoption, path reopening from verifier output, host libc substitution, fabricated configuration header or fallback runtime. Charge actual retained, expanded and output work under the original selected counter/end. Latch the first raw error, independently retire partial resources and refuse renewed admission after failure.

Acceptance criteria

  • Assemble from the same live authenticated archive receivers, preserving the Rust-fork unwinder and exact project source identities and legal records.
  • Reject unsafe members, occupied/foreign outputs, mutated/restored inputs, foreign or withdrawn receivers, missing target/sysroot/port/tool inputs and unresolved deployment before untrusted execution.
  • Produce fixed runtime-first configure/build/install invocations with explicit original inputs; do not silently use host headers/libraries or disable required functionality.
  • Cover genuine harmless file/effect ownership, partial writes, native failure and once-only retirement. Document source, output, tools, lifetimes and trust anchors.
  • Keep actual EriX runtime compilation, link closure, allocation/TLS/thread/exception execution and guest rebuild visibly pending until demonstrated.

Alternatives and tradeoffs

Reopening the verifier report loses source custody. Replacing the whole LLVM tree loses Rust's unwinder changes. A host-libc experiment may diagnose upstream configuration but cannot satisfy EriX runtime acceptance. Explicit unresolved inputs are preferable to a passing reduced configuration.

Tracking and rollout

Depends on source input design #608 and source admission #610. Implement the original source assembly and effect pipeline together, then provision independently selected EriX target/port/sysroot products before runtime execution.

## Problem and motivation The admitted C++ archives and runtime-first graph declarations do not yet supply a live source assembly or executable runtime recipe. A verifier's JSON cannot carry original file custody into a compiler invocation. ## Proposed behavior and scope Extend the existing toolchain source feature with an original bounded runtime operation. Retain the exact catalog, runtime policy, Rust source and matching libc++/libc++abi archive receivers through fresh source assembly and runtime effects. Preserve the Rust fork's compiler-rt, libunwind, CMake and runtimes sources. Add only the two explicitly selected missing project trees in an external output namespace; never overwrite the Rust source. Bind configure/build/install steps to explicitly admitted compiler, CMake/Ninja, target configuration, EriX sysroot and port products. Keep static/shared deployment explicit and fail before upstream execution when required inputs are unresolved. Retain localization, wide characters, Unicode, threads, filesystem, exceptions and RTTI. Compilation and guest rebuilding remain acceptance gates rather than source-control results. ## Authority, security and reliability Register actual input/output receivers before effects. Source digests, paths and recipe records remain data, never owners. Use held descriptors and current original byte/namespace checks at assembly and native admission/settlement; hold all source, tool and product inputs until actual native retirement. No serialized receipt adoption, path reopening from verifier output, host libc substitution, fabricated configuration header or fallback runtime. Charge actual retained, expanded and output work under the original selected counter/end. Latch the first raw error, independently retire partial resources and refuse renewed admission after failure. ## Acceptance criteria - Assemble from the same live authenticated archive receivers, preserving the Rust-fork unwinder and exact project source identities and legal records. - Reject unsafe members, occupied/foreign outputs, mutated/restored inputs, foreign or withdrawn receivers, missing target/sysroot/port/tool inputs and unresolved deployment before untrusted execution. - Produce fixed runtime-first configure/build/install invocations with explicit original inputs; do not silently use host headers/libraries or disable required functionality. - Cover genuine harmless file/effect ownership, partial writes, native failure and once-only retirement. Document source, output, tools, lifetimes and trust anchors. - Keep actual EriX runtime compilation, link closure, allocation/TLS/thread/exception execution and guest rebuild visibly pending until demonstrated. ## Alternatives and tradeoffs Reopening the verifier report loses source custody. Replacing the whole LLVM tree loses Rust's unwinder changes. A host-libc experiment may diagnose upstream configuration but cannot satisfy EriX runtime acceptance. Explicit unresolved inputs are preferable to a passing reduced configuration. ## Tracking and rollout Depends on [source input design #608](https://git.erikinkinen.fi/erix/integration/issues/608) and [source admission #610](https://git.erikinkinen.fi/erix/integration/pulls/610). Implement the original source assembly and effect pipeline together, then provision independently selected EriX target/port/sysroot products before runtime execution.
erikinkinen added this to the Alpha 1 milestone 2026-11-08 18:05:14 +01:00
Sign in to join this conversation.
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
erix/integration#616
No description provided.