Compiling android fails trying to contact jack

Message

shaumux · Post by **shaumux** » Sun Mar 12, 2017 1:22 pm

I'm trying to compile android on gentoo, it progresses and then fails on jack server.
The error seems to be because of curl/openssl

The error is

Code: Select all

*   Trying 127.0.0.1...
* TCP_NODELAY set
* Connected to 127.0.0.1 (127.0.0.1) port 8077 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /home/shaumux/.jack-server/server.pem
  CApath: /etc/ssl/certs
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* Unknown SSL protocol error in connection to 127.0.0.1:8077 
* stopped the pause stream!
* Closing connection 0

curl is built with

Code: Select all

curl 7.53.1 (x86_64-pc-linux-gnu) libcurl/7.53.1 OpenSSL/1.0.2k zlib/1.2.11 c-ares/1.12.0 libidn2/0.16 libssh2/1.8.0 nghttp2/1.20.0 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy

Use flags for curl:

Code: Select all

USE="adns http2 idn ipv6 kerberos ldap rtmp samba ssh ssl -metalink -static-libs {-test} -threads" ABI_X86="32 (64) (-x32)" CURL_SSL="openssl -axtls -gnutls -libressl -mbedtls -nss -polarssl (-winssl)"

use flags for openssl

Code: Select all

USE="asm rfc3779 sctp sslv2 sslv3 tls-heartbeat zlib -bindist -gmp -kerberos -static-libs {-test} -vanilla" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="(sse2)"

Any idea anyone?

devsk · Post by **devsk** » Sun May 14, 2017 8:16 am

Strange! I am also running into SSL issues between curl and the jack-server but my connection is not even established to port 8077. I get:

Code: Select all

[ 10% 1904/18030] Ensure Jack server is installed and started
FAILED: setup-jack-server
/bin/bash -c "(prebuilts/sdk/tools/jack-admin install-server prebuilts/sdk/tools/jack-launcher.jar prebuilts/sdk/tools/jack-server-4.8.ALPHA.jar  2>&1 || (exit 0) ) && (JACK_SERVER_VM_ARGUMENTS=\"-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx8G\" prebuilts/sdk/tools/jack-admin start-server 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update server prebuilts/sdk/tools/jack-server-4.8.ALPHA.jar 4.8.ALPHA 2>&1 || exit 0 ) && (prebuilts/sdk/tools/jack-admin update jack prebuilts/sdk/tools/jacks/jack-2.28.RELEASE.jar 2.28.RELEASE || exit 47; prebuilts/sdk/tools/jack-admin update jack prebuilts/sdk/tools/jacks/jack-3.36.CANDIDATE.jar 3.36.CANDIDATE || exit 47; prebuilts/sdk/tools/jack-admin update jack prebuilts/sdk/tools/jacks/jack-4.7.BETA.jar 4.7.BETA || exit 47 )"
Jack server already installed in "/home/devsk/.jack-server"
Launching Jack server java -XX:MaxJavaStackTraceDepth=-1 -Djava.io.tmpdir=/tmp -Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx8G -cp /home/devsk/.jack-server/launcher.jar com.android.jack.launcher.ServerLauncher
Jack server failed to (re)start, try 'jack-diagnose' or see Jack server log
SSL error when connecting to the Jack server. Try 'jack-diagnose'
SSL error when connecting to the Jack server. Try 'jack-diagnose'

So far, no resolution.

devsk · Post by **devsk** » Sun May 14, 2017 8:33 am

Oh wait...I actually get the same error. I looked at the error code using curl -v and it showed exactly what you got.

Did you by any chance find a fix?

nvertigo · Post by **nvertigo** » Sun May 14, 2017 12:56 pm

I'm in the same situation: after 18 month successfully building android - yesterday jack started to fail with the above error. I'm using icedtea:8 with default use flags. Out of desperation I installed icedtea-bin:8 and communication with jack-server worked again.

Will check now building icedtea:8 without pch and sunec. Will report later, wanted to share this "hotfix" first.

devsk · Post by **devsk** » Sun May 14, 2017 7:33 pm

Dang!! Moving to icedtea-bin made the jack server work again. Thank you so much for that tip!!

nvertigo · Post by **nvertigo** » Mon May 15, 2017 7:09 am

I checked icedtea:8 with different USE flags to no avail. Sadly I'm low on time, and can't do the same for openssl. This should also be checked. I havn't checked building with libressl instead of open ssl. If anything fails to get the source build icedtea working, someone should create an bug report.

I'm not lazy - just busy (building and maintaining this oneplis3t rom: https://forum.xda-developers.com/oneplu ... 1-t3547024 ).

On a side note: using icedtea-bin:8 fixes also the broken ssl connections with android-sdk-update-manager.

I'm afraid the source build icedtea:8 is breaking ssl in java all together.

Ivanich_ · Post by **Ivanich_** » Fri May 19, 2017 6:09 pm

nvertigo wrote:I checked icedtea:8 with different USE flags to no avail. Sadly I'm low on time, and can't do the same for openssl. This should also be checked. I havn't checked building with libressl instead of open ssl. If anything fails to get the source build icedtea working, someone should create an bug report.

I'm not lazy - just busy (building and maintaining this oneplis3t rom: https://forum.xda-developers.com/oneplu ... 1-t3547024 ).

On a side note: using icedtea-bin:8 fixes also the broken ssl connections with android-sdk-update-manager.

I'm afraid the source build icedtea:8 is breaking ssl in java all together.

gnutls-3.5.12 caused this, however last working gnutls-3.5.11 is removed from tree today.

nvertigo · Post by **nvertigo** » Fri May 26, 2017 11:25 am

Ivanich_ wrote: gnutls-3.5.12 caused this, however last working gnutls-3.5.11 is removed from tree today.

I was on gnutls-3.3.20 when the ssl error occured first.

Ivanich_ · Post by **Ivanich_** » Sat May 27, 2017 9:38 am

nvertigo wrote:
Ivanich_ wrote: gnutls-3.5.12 caused this, however last working gnutls-3.5.11 is removed from tree today.
I was on gnutls-3.3.20 when the ssl error occured first.

It was nss incompatibility but simple workaround is to rebuild icedtea with new nss, however this is not an issue anymore.
Now I run into this trouble with gnutls, had to downgrade to 3.5.11 in order to build android.
BTW, building roms for op3

Ivanich_ · Post by **Ivanich_** » Sun Mar 25, 2018 10:06 am

Ivanich_ wrote:
nvertigo wrote:
Ivanich_ wrote: gnutls-3.5.12 caused this, however last working gnutls-3.5.11 is removed from tree today.
I was on gnutls-3.3.20 when the ssl error occured first.
It was nss incompatibility but simple workaround is to rebuild icedtea with new nss, however this is not an issue anymore.
Now I run into this trouble with gnutls, had to downgrade to 3.5.11 in order to build android.
BTW, building roms for op3

Answer to myself in case someone has similar issue, solution is to set

Code: Select all

CURL_SSL="openssl"

in make.conf and rebuild curl.
When set to gnutls it wouldn't work.

kernelOfTruth · Post by **kernelOfTruth** » Sun May 27, 2018 5:15 pm

How is this stupid error still happening

(can't build Android beyond gnutls 3.5.11)

Ivanich_ wrote:
Ivanich_ wrote:
nvertigo wrote: I was on gnutls-3.3.20 when the ssl error occured first.
It was nss incompatibility but simple workaround is to rebuild icedtea with new nss, however this is not an issue anymore.
Now I run into this trouble with gnutls, had to downgrade to 3.5.11 in order to build android.
BTW, building roms for op3
Answer to myself in case someone has similar issue, solution is to set
Code: Select all
CURL_SSL="openssl"
in make.conf and rebuild curl.
When set to gnutls it wouldn't work.

gotta test this - thanks