On Sat, 5 Mar 2022 12:44:36 GMT, Julian Waters <jwat...@openjdk.org> wrote:
> Some of the --without options are not properly handled and will crash when > processed (For example, --without-version-string), in other cases the > --without-* option will actually silently produce incorrect results instead > of actually doing what --without-* implies (For example, --without-build-user > and all the --with-vendor-* options). The most elegant way to solve this > would simply be to handle such cases and display warnings when they're > encountered (or if the option is critical to the build process, throwing an > error) > > Even if it doesn't make sense to pass said option however, it should display > a warning instead of letting configure exit with a confusing error when it's > run This pull request has now been integrated. Changeset: cab9def1 Author: Julian Waters <jwat...@openjdk.org> Committer: Magnus Ihse Bursie <i...@openjdk.org> URL: https://git.openjdk.java.net/jdk/commit/cab9def1c1ab28b0b1a8cf268d0853f6e2bfa77f Stats: 18 lines in 1 file changed: 5 ins; 0 del; 13 mod 8282700: Properly handle several --without options during configure Reviewed-by: ihse ------------- PR: https://git.openjdk.java.net/jdk/pull/7713
