On 11/04/2019 15:21, Christopher Schultz wrote:
<snip/>
> I'm having a bit of trouble building the bundled tcnative. I'm tried
> building against OpenSSL 1.0.2k and 1.1.1 and both of the "configure"
> invocations given me a message similar to the following:
>
> checking for OpenSSL library... using openssl from
> /home/cschultz/openssl-1.0.2k/target/target/${exec_prefix}/lib and
> /home/cschultz/openssl-1.0.2k/target/target/include
> checking OpenSSL library version >= 1.0.2... configure: error: Your
> version of OpenSSL is not compatible with this version of tcnative
>
> Any ideas for what to check? That ${exec_prefix} in there looks a little
> fishy. Here's my configure command:
>
> ./configure --with-apr=/usr/bin
> --with-ssl=/home/cschultz/openssl-1.0.2k/target/target
That looks odd with 2 targets on the end.
> --with-java-home=/usr/lib/jvm/java-8-openjdk-amd64
I did a little testing with this.
I agree the ${exec_prefix} looks odd but it doesn't appear to be
breaking anything.
When I provide a valid path to an OpenSSL build everything works as
expected (1.0.2, 1.1.0, 1.1.1 and master).
When I provide an invalid path to an OpenSSL build then it appears to
pick up up the version of OpenSSL installed by the OS.
I see two (minor) problems we could fix:
1. The ${exec_prefix} oddity
2. If an invalid OpenSSL path is specified the build should fail rather
than pick up a system default.
Given that everything appears to work as intended with valid input, I
don't see any immediate need to roll a Tomcat Native release.
Thoughts?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
