On Wed, 5 Mar 2025 22:59:06 GMT, Jiangli Zhou <jian...@openjdk.org> wrote:
> Please review this PR that excludes `libjsig` from being statically linked > with `static-jdk` `java` launcher by default. Please see details in > https://bugs.openjdk.org/browse/JDK-8351309 description and comments. Thanks I meant more like "not supported". You are correct that it is technically possible. How useful is signal chaining even these days? While we could do something like this, I see more trouble ahead. How should we do when we put the static libs in a jmod? Should all static libraries have an "optional/required" flag attached to them? How do the user select if libjsig should be included or not? I would argue that for the time being, it is better to set libjsig as `ONLY_EXPORTED`, and if/when we get back to revisit this, we can start compiling it always, and then we will also have a story on how to test it, how to handle it in jmods, etc, including perhaps a better idea on how important it is to have signal chaining for static builds. ------------- PR Comment: https://git.openjdk.org/jdk/pull/23924#issuecomment-2704678008
