gzm55 commented on issue #888: URL: https://github.com/apache/maven-mvnd/issues/888#issuecomment-1873664250
> I'm sorry that I do not specialize in native programming. So, I'm unsure if my build only requires glibc@2.12. > > But I built the project followed by the official workflow (https://github.com/apache/maven-mvnd/blob/1.0-m7/.github/workflows/release.yaml#L67) which contains #825 that solves #823. > > I just replaced all `amd64` or `x86_64` with `aarch64` after this patch. > > Then everything was fine, even the `Verify native binary for only requiring glibc 2.12` script passed. (https://github.com/apache/maven-mvnd/blob/1.0-m7/.github/workflows/release.yaml#L91). > > When I copy the target to another aarch64 machine that runs Kylin-OS (a Linux distribution that seems like CentOS 8), it still works fine. > > It is worth mentioning that my `PAGE_SIZE` is 64k rather than 4k (maybe 4k is more common). So I have to set `-H:PageSize=65536`. We can get more information from [oracle/graal#5605](https://github.com/oracle/graal/pull/5605) For aarch64 arch, the oldest public released glibc is glibc-2.17 for CentOS7. It is reasonable that we limit the running glibc >= 2.17 on aarch64 cpu. But the resource should be upload for each hardware (x64/arm64). Also the UT in CI could be improved to check dependencies strictly for each arch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
