On Sun, 11 Oct 2026 06:15:10 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).

This pull request has now been integrated.

Changeset: b235d143
Author:    Yunbo Zhang <[email protected]>
Committer: Aleksey Shipilev <[email protected]>
URL:       
https://git.openjdk.org/jdk/commit/b235d1432a1fd47f6856ece7b4bb4aaab963f5a9
Stats:     17 lines in 2 files changed: 14 ins; 0 del; 3 mod

8387719: Building the JDK: running `bash configure` does not detect musl

Reviewed-by: shade

-------------

PR: https://git.openjdk.org/jdk/pull/33300

Reply via email to