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
The way #1321 is going, we're going to introduce a musl-targeting C toolchain for each of our linux fips platforms (linux_amd64 and linux_arm64).
Building the toolchain from source in CI has a number of issues. Primarily, though, the issue is that it will be flaky. Downloading the source of gcc, musl, and a half dozen c libraries from miscellaneous mirrors is not always quick, and the mirrors seem to be less than reliable. If this becomes a huge issue we could find a way to cache sources and or the whole toolchain ourselves.
It'd be better to nix the idea of building our own toolchains all-together, and simply use the toolchain that comes packaged with alpine linux, alpine-sdk (native only.) When we get access to aarch64 builders we can tear out all of the toolchain building infrastructure and run the same make command but in an alpine container. A very crude and likely non-functional version of this may look like this:
The way #1321 is going, we're going to introduce a musl-targeting C toolchain for each of our linux fips platforms (linux_amd64 and linux_arm64).
Building the toolchain from source in CI has a number of issues. Primarily, though, the issue is that it will be flaky. Downloading the source of gcc, musl, and a half dozen c libraries from miscellaneous mirrors is not always quick, and the mirrors seem to be less than reliable. If this becomes a huge issue we could find a way to cache sources and or the whole toolchain ourselves.
It'd be better to nix the idea of building our own toolchains all-together, and simply use the toolchain that comes packaged with alpine linux, alpine-sdk (native only.) When we get access to aarch64 builders we can tear out all of the toolchain building infrastructure and run the same make command but in an alpine container. A very crude and likely non-functional version of this may look like this:
The text was updated successfully, but these errors were encountered: