Closed Xeonacid closed 4 months ago
The use of old Debian versions for the build environment is purposefully: it ensures we don't reference too-new glibc symbol versions. (Strictly speaking we could use something like zig cc
to achieve glibc version targeting without actually compiling against an ancient glibc, but the tried-and-true method of compile on an older distro/glibc is what I went with initially.)
To build out riscv64 support, we can introduce a separate base image (one based on Debian 10 perhaps?) and use it to build riscv64.
Thanks!
Hi, I'm adding support for RISC-V. But https://github.com/indygreg/python-build-standalone/blob/main/cpython-unix/build.cross.Dockerfile#L2 uses a very old image, Debian 9 "Stretch", which has been EOL in June 30, 2022. And it has no riscv64 cross compiler in apt repo. Could we bump the base image (and https://github.com/indygreg/python-build-standalone/blob/main/cpython-unix/build.cross.Dockerfile#L24 snapshot OFC) to a newer, in support one?
BTW, https://github.com/indygreg/python-build-standalone/blob/main/cpython-unix/base.Dockerfile#L2 uses an even older one, Debian 8 "Jessie"...