You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9256260
Browse filesBrowse the repository at this point in the historyBrowse files
chore: bump version to 2026.8.17.1, and record what §1–§4 actually became
The design doc gains a status section per item, including the two places the
PLAN was corrected by the implementation and the one half of §4 that was
deliberately not done:
- `dist::Format` now reads the target triple before falling back to the host.
Everything but MinGW used to ask the host, which made a Windows contract
unassertable on the Linux runner where most of this gets reviewed. It only
ADDS answers, so no existing build changes.
- `force_bundle` had to reach the PE system list too. ELF always worked that
way; making the PE exclusion unconditional would have turned an explicitly
written decision into decoration.
- The ELF closure still runs the artifact. `ldd` hands back RESOLVED PATHS
while `DT_NEEDED` gives only names, and turning names into paths means
reimplementing the loader's search order ($ORIGIN, DT_RPATH before
LD_LIBRARY_PATH before DT_RUNPATH before ld.so.cache, hwcaps). Rewriting
that under a correct, e2e-covered path is more risk than it buys — and the
cost is stated rather than left to be discovered: cross-ARCHITECTURE ELF
packing is still unsupported, which is the second limit §4.1 names.
`mcpp self doctor` reports the Windows SDK PER ORIGIN. One unlabelled line was
the same "one question, two answerers" shape this axis exists to close: a user
reading it would believe it applied to their pinned build, and it did not.
0 commit comments