Am 12.12.2015 um 18:29 schrieb Nithesh Kb:
HI Rainer,
Interestingly i tried this as well.
*APR,*
*CC="cc" CFLAGS="-m64" LDFLAGS="-m64" ./configure*
*TC-native,*
*CC="cc" CFLAGS="-m64 -fPIC" LDFLAGS="-m64" ./configure
--with-apr=/usr/local/apr/bin/apr-1-config
--with-java-home=/usr/jdk/jdk1.7.0_80/ --with-ssl=/usr/local/ssl
--prefix=/tomcat*
*But i get this error,*
*ld: fatal: file /usr/local/ssl/lib/libssl.so: wrong ELF class: ELFCLASS32*
*ld: fatal: file /usr/local/ssl/lib/libcrypto.so: wrong ELF class:
ELFCLASS32*
*ld: fatal: file processing errors. No output written to
.libs/libtcnative-1.so.0.1.33*
**** Error code 2*
*make: Fatal error: Command failed for target `libtcnative-1.la
<http://libtcnative-1.la>'*
*Current working directory /tomcat/bin/tomcat-native-1.1.33-src/jni/native*
Does it mean my openssl is not 64 bit, actually i'm not sure about my
openssl architecture ?
Yes, that's why I suggested you should build OpenSSL as well. It will
not have any further dependencies.
You can check bitness using
file /usr/local/ssl/lib/libssl.so
file /usr/local/ssl/lib/libcrypto.so
Pick yourself a 1.0.2e OpenSSl download, build it (with -m64) and
install it into a separate directory. Check the bitness of the result
with the "file" command. Then point tcnative at it when running its
configure etc.
You are pretty close.
Note that there's also a more recent tcnative 1.2.2 and the versions
1.3.34 and 1.2.3 are currently in the voting process, so will likely be
released very soon. So once your build works, you might want to check
for the recent version and redo the build. You can use the same APR and
OpenSSL builds, so no need to redo them for the nex tcnative.
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
