This is an automated email from the ASF dual-hosted git repository. remm pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/tomcat.git
The following commit(s) were added to refs/heads/master by this push: new d34e682 Document the limitation of --static native image compilation d34e682 is described below commit d34e682de65f0b8d45f2e392231a5704564957b7 Author: remm <r...@apache.org> AuthorDate: Tue Jul 16 17:15:55 2019 +0200 Document the limitation of --static native image compilation No TLS support is possible in that case, as far as I can see (SunEC is dynamic, and tomcat-native can be static but JNI cannot use that). --- res/tomcat-maven/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/res/tomcat-maven/README.md b/res/tomcat-maven/README.md index aed08d7..a3741a5 100644 --- a/res/tomcat-maven/README.md +++ b/res/tomcat-maven/README.md @@ -109,4 +109,5 @@ $JAVA_HOME/bin/native-image --no-server --allow-incomplete-classpath --enable-ht Running in a container is possible, an example `DockerfileGraal` is given. To use a native image in a container that is not identical to the build platform, the `native-image` call will need to use the additional `--static` parameter to statically link libraries (this will then require zlib and glibc -static libraries). +static libraries). Due to TLS needing dynamic libraries (SunEC or tomcat-native), TLS support is not available. If TLS support is needed, the native +image must instead be built on the target platform (see the GraalVM documentation for building a native image in a container). --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org