[BUG] Dynamic service builds discard Cargo dependency aliases #111

Closed
opened 2026-10-12 19:23:04 +02:00 by erikinkinen · 1 comment
Owner

Summary

Dynamic service builds discard Cargo dependency aliases. E2fsd and Fatd consequently fail to compile, preventing 506 of the 524 selected VM scenarios from running.

Reproduction

Run the Integration CI workflow at 5cdd151b807b2e3bfc914d58c40fb7da413eb49c with its selected source graph. The release dynamic builds of E2fsd and Fatd fail before image construction.

Expected and actual behavior

The compiler should receive each dependency under the name declared in the service manifest. E2fsd declares constant_time, but the builder supplies lib_constant_time; Fatd declares lib-sha2, but the builder supplies sha2. Rust reports E0433 for constant_time and lib_sha2 and exits unsuccessfully.

Environment and identity

  • Integration: 5cdd151b807b2e3bfc914d58c40fb7da413eb49c.
  • E2fsd: 64fc1c3412981bc22a175be2079061ddd76d9b12; Fatd: 4105c9aa6719094587adb3421314d0d822ff7583.
  • Release PIC service compilation for x86_64-unknown-none, with explicit shared-object registry and dependency records. No guest authority is exercised.

Evidence and prior checks

CI run 2479 passes the host gates and then reports the same two missing crate names across its VM workers. The shared objects and both direct dependency records are present; compiler alias selection ignores the service manifests.

Tracking

Derive service extern names from the selected Cargo manifests and retain metadata consistency, strict warning rejection and the ban on statically bundled dependency code.

## Summary Dynamic service builds discard Cargo dependency aliases. E2fsd and Fatd consequently fail to compile, preventing 506 of the 524 selected VM scenarios from running. ## Reproduction Run the Integration CI workflow at `5cdd151b807b2e3bfc914d58c40fb7da413eb49c` with its selected source graph. The release dynamic builds of E2fsd and Fatd fail before image construction. ## Expected and actual behavior The compiler should receive each dependency under the name declared in the service manifest. E2fsd declares `constant_time`, but the builder supplies `lib_constant_time`; Fatd declares `lib-sha2`, but the builder supplies `sha2`. Rust reports E0433 for `constant_time` and `lib_sha2` and exits unsuccessfully. ## Environment and identity - Integration: `5cdd151b807b2e3bfc914d58c40fb7da413eb49c`. - E2fsd: `64fc1c3412981bc22a175be2079061ddd76d9b12`; Fatd: `4105c9aa6719094587adb3421314d0d822ff7583`. - Release PIC service compilation for `x86_64-unknown-none`, with explicit shared-object registry and dependency records. No guest authority is exercised. ## Evidence and prior checks [CI run 2479](https://git.erikinkinen.fi/erix/integration/actions/runs/2479) passes the host gates and then reports the same two missing crate names across its VM workers. The shared objects and both direct dependency records are present; compiler alias selection ignores the service manifests. ## Tracking Derive service extern names from the selected Cargo manifests and retain metadata consistency, strict warning rejection and the ban on statically bundled dependency code.
Author
Owner

The fix uses each service manifest's names for its recorded direct imports in both library and binary compilation. Both selected E2fsd and Fatd now produce release dynamic ELFs, and all 13 actual artifacts pass strict metadata inspection. Original metadata conflict checks, warning rejection and dependency code exclusion remain. The remaining full VM and image checks are tracked separately.

The [fix](https://git.erikinkinen.fi/erix/integration/commit/9401e0f3690e7094780decfb7919caf467ca7fe2) uses each service manifest's names for its recorded direct imports in both library and binary compilation. Both selected E2fsd and Fatd now produce release dynamic ELFs, and all 13 actual artifacts pass strict metadata inspection. Original metadata conflict checks, warning rejection and dependency code exclusion remain. The remaining full VM and image checks are tracked separately.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:16 +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#111
No description provided.