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 5fe9555 Better wording for --static problems
5fe9555 is described below
commit 5fe95550d36f53ebe341bf20ea5ce50306b76f52
Author: remm <[email protected]>
AuthorDate: Tue Jul 16 23:11:14 2019 +0200
Better wording for --static problems
---
res/tomcat-maven/README.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/res/tomcat-maven/README.md b/res/tomcat-maven/README.md
index a3741a5..4188ed9 100644
--- a/res/tomcat-maven/README.md
+++ b/res/tomcat-maven/README.md
@@ -108,6 +108,6 @@ $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). 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).
+the `native-image` call will need to use the additional `--static` parameter
to statically link base libraries (this will then require zlib and glibc
+static libraries). Due to TLS using dynamic libraries (SunEC for JSSE and
tomcat-native for OpenSSL), TLS support is not available with static linking.
+If TLS support is needed, the native image must instead be built on a platform
identical to the target platform.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
