Repository navigation
0.2.0: GNU/Hurd and Haiku (x86_64-hurd, x86_64-haiku), with import std and a runner each - #5
Merged
Merged
Conversation
…d and a runner each Two systems move here from the external validation project's own platforms (ChenPi11/cmd fork, mcpp/platforms/), as docs/adding-a-system.md states a system: the system, a row, a provider over a sysroot package of xim and a dirun runner over the system's disk image, enabled on request. - GNU/Hurd: Debian's hurd-amd64 base at the package versions of Debian's pre-installed image of 2026-03-14 (xim x86_64-hurd-sysroot@20260314), run in that image (hurd-disk-image@20260314). The compiler's run-time is the base's libgcc (cfg(os = "hurd") ldflags). - Haiku: hrev60431's base with GCC's run-time from HaikuPorts (x86_64-haiku-sysroot@hrev60431, revision 1), run in an image of the same revision (haiku-disk-image@hrev60431). Both bases state GCC 15's std module sources, so both rows compile import std (openxlings/xim-pkgindex#1194). Measured on Linux x86_64: the check (import std, an exception, its arguments) built for each row and run in the system's image returned 7. CI builds both rows on the four hosts and runs them on Linux x86_64.
Measured in this PR's CI: on Windows the std module's precompile of a libstdc++ base gets neither its include directories nor -nostdinc++ (mcpp-community/mcpp#965); on macOS, whose default file system is case-insensitive, Haiku's <string.h> is its BeAPI String.h, since clang's Haiku driver searches os/support before posix. CI does not build those three pairs; docs/adding-a-system.md and the README state them.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two systems move here from the external validation project's own platforms (the ChenPi11/cmd fork's
mcpp/platforms/), stated asdocs/adding-a-system.mdasks: the system, a row, a provider over a sysroot package of xim, and a dirun runner over the system's disk image, enabled on request.x86_64-hurdxim:x86_64-hurd-sysroot@20260314: Debian's hurd-amd64 at the package versions of Debian's pre-installed image of 2026-03-14hurd-disk-image@20260314)x86_64-haikuxim:x86_64-haiku-sysroot@hrev60431(revision 1)haiku-disk-image@hrev60431)import stdBoth bases state GCC's std module sources with libstdc++'s include directories (openxlings/xim-pkgindex#1194):
<fenv.h>defines seven functionsstatic __inline; its sysroot gives them external linkage in C++, so the std module can export them.GLIBCXX_3.4.36' not found.Measured locally (Linux x86_64)
The check (
import std, an exception, its arguments), built for each row and run in the system's image through dirun, returned 7. The validation project's batch script (C) ran on both with the expected output.CI builds both rows on the four hosts and runs them on Linux x86_64. The macOS and Windows builds of these two rows have not been measured before this PR.