Am 19.04.2016 um 12:17 schrieb Rainer Jung:
Am 19.04.2016 um 11:35 schrieb Rainer Jung:
I just now saw, that there's again an API break for OpenSSL 1.1.0.

I'll try to fix that during the next hour.

I don't understand the Gump failure for tcnative trunk which happened
this night. The errors look like tcnative trunk has been compiled
against a mixture of header files from OpenSSL master and older, but the
OpenSSL build logs on Gump don't indicate any such error.

For example the first build error was:

/bin/bash /srv/gump/public/workspace/apr-1/dest-20160419/build-1/libtool
--silent --mode=compile gcc -g -O2 -pthread   -DHAVE_CONFIG_H  -DLINUX
-D_REENTRANT -D_GNU_SOURCE   -g -O2 -DHAVE_OPENSSL -DHAVE_POLLSET_WAKEUP
   -I/srv/gump/public/workspace/tomcat-native-trunk/native/include
-I/usr/lib/jvm/java-8-oracle/include
-I/usr/lib/jvm/java-8-oracle/include/linux
-I/srv/gump/public/workspace/openssl-master/dest-20160419/include
-I/srv/gump/public/workspace/apr-1/dest-20160419/include/apr-1   -o
src/ssl.lo -c src/ssl.c && touch src/ssl.lo

In file included from src/ssl.c:17:0:
src/ssl.c: In function 'Java_org_apache_tomcat_jni_SSL_versionString':
src/ssl.c:312:43: error: 'OPENSSL_VERSION' undeclared (first use in this
function)
      return AJP_TO_JSTRING(OpenSSL_version(OPENSSL_VERSION));

But the OpenSSL master snapshots for 20160418 and 20140619 contain the line

# define OPENSSL_VERSION          0

in openssl/crypto.h and there have been no more recent changes to the
OpenSSL master on github from which Gump gets its files.

Konstantin has pointed out on otherthread, that Gump has some issues with stale git pulled resources currently. The build failures during last night look to me, as they wouldn't happen with a recent OpenSSL master checkout (and they don't happen for me locally).

So IMHO we are good to go.

Regards,

Rainer



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to