Cross-platform build portability
This is a tracking issue for defects that cause build or runtime failures on
specific platforms (Linux, macOS, aarch64) due to missing platform guards in
the build configuration.
Child issues
| Issue |
Locus |
Status |
#43 — windows-sys not target-gated |
lore-client:21, lore:32, lore-base:37, lore-revision:61 Cargo.toml |
PR #45 open |
#30 — CLI mojibake in lore history on Windows |
lore-client/src/cli/terminal_size.rs, print_macros.rs |
No PR |
| #42 — aarch64 runtime crash after self-compile |
lore-base/build.rs:28–29 (-mcpu=neoverse-512tvb) |
Pending classification |
Shared pattern
Each item results from a build-time or startup configuration that lacks a
platform guard, causing failure on platforms outside the intended target.
windows-sys gating (#43):
lore-storage/Cargo.toml:47–48 and lore-credential/Cargo.toml:28–29 are
the correct reference: [target.'cfg(target_os = "windows")'.dependencies].
Four crates declare windows-sys as an unconditional dependency, adding a
Windows-only transitive dependency to non-Windows builds. PR #45 is open.
CLI mojibake (#30):
The Windows console defaults to a legacy code page on many configurations.
Adding SetConsoleOutputCP(CP_UTF8) under #[cfg(target_os = "windows")] at
CLI startup is the standard fix.
aarch64 crash (#42):
lore-base/build.rs:28–29 passes -mcpu=neoverse-512tvb unconditionally to
the C compiler. The Neoverse 512TVB microarch enables SVE2 and other
extensions not available on all aarch64 hardware. Binaries compiled with this
flag crash with illegal hardware instruction on hardware that does not
implement those extensions. The flag should be gated on a CPU-capability check
or a cargo:warning= should alert the user that their hardware does not
support this build path.
Fix directions
Background
Identified in the open-bug theme analysis (triage/2026-06-bug-theme-analysis.md,
branch valentina2509:docs/bug-theme-analysis).
Cross-platform build portability
This is a tracking issue for defects that cause build or runtime failures on
specific platforms (Linux, macOS, aarch64) due to missing platform guards in
the build configuration.
Child issues
windows-sysnot target-gatedCargo.tomllore historyon Windowslore-client/src/cli/terminal_size.rs,print_macros.rslore-base/build.rs:28–29(-mcpu=neoverse-512tvb)Shared pattern
Each item results from a build-time or startup configuration that lacks a
platform guard, causing failure on platforms outside the intended target.
windows-sysgating (#43):lore-storage/Cargo.toml:47–48andlore-credential/Cargo.toml:28–29arethe correct reference:
[target.'cfg(target_os = "windows")'.dependencies].Four crates declare
windows-sysas an unconditional dependency, adding aWindows-only transitive dependency to non-Windows builds. PR #45 is open.
CLI mojibake (#30):
The Windows console defaults to a legacy code page on many configurations.
Adding
SetConsoleOutputCP(CP_UTF8)under#[cfg(target_os = "windows")]atCLI startup is the standard fix.
aarch64 crash (#42):
lore-base/build.rs:28–29passes-mcpu=neoverse-512tvbunconditionally tothe C compiler. The Neoverse 512TVB microarch enables SVE2 and other
extensions not available on all aarch64 hardware. Binaries compiled with this
flag crash with
illegal hardware instructionon hardware that does notimplement those extensions. The flag should be gated on a CPU-capability check
or a
cargo:warning=should alert the user that their hardware does notsupport this build path.
Fix directions
windows-sysdependencies on Windows targets and fix UTF-8 terminal output #45 forwindows-sysgating; verify that theWin32_*featuresubsets differ per crate and update each independently.
SetConsoleOutputCP(CP_UTF8)at CLI startup on Windows (can beincluded in PR Gate
windows-sysdependencies on Windows targets and fix UTF-8 terminal output #45 or a follow-up PR).lore-base/build.rs:28–29and gate the microarch flagappropriately for the aarch64 target.
Background
Identified in the open-bug theme analysis (triage/2026-06-bug-theme-analysis.md,
branch
valentina2509:docs/bug-theme-analysis).