On Tue, 13 Oct 2026 08:19:13 GMT, Yunbo Zhang <[email protected]> wrote:
>> Please review this small build fix. >> >> `configure` reports `default` instead of `musl` for targets ending in >> `linux-musleabi` or `linux-musleabihf`. >> >> **Fix:** >> >> `PLATFORM_EXTRACT_VARS_FROM_LIBC` now uses `*linux*-musl*` and >> `*linux*-gnu*` to accept ABI suffixes. >> >> **Testing:** >> >> - `make test-make`: passed. >> - Added libc detection coverage to the existing Autoconf tests >> (`linux-musl`, `linux-musleabi`, `linux-musleabihf`, `linux-gnu`, >> `linux-gnueabi`, `linux-gnueabihf`, `linux-gnuabi64`). >> - ARM32 musl cross-configure with an explicit >> `--openjdk-target=armv7l-unknown-linux-musleabihf`: reported `musl` after >> the fix. >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Yunbo Zhang has updated the pull request incrementally with one additional > commit since the last revision: > > 8387719: Building the JDK: running `bash configure` does not detect musl > > Also recognize GNU libc names with ABI suffixes and extend the configure > tests. @benshuai5D Your change (at version 4e764fe9f08a05ea70183bcc702fd1d4af6b0f15) is now ready to be sponsored by a Committer. ------------- PR Comment: https://git.openjdk.org/jdk/pull/33300#issuecomment-6144839812
