-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Openssl build now fails in Tor build script. #2314
Comments
A standalone openssl build is broken for more than a week as well: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14075 @kroeckx do you know what could've changed? |
I've just filed openssl/openssl#8735, which I think is the problem. |
Thanks! I'll keep an eye on it. |
openssl/openssl#8749 landed but openssl and tor builds still failing. |
Recent envoy and Tor builds have been succeeding. @Dor1s I think this can be closed right? |
Yes, Sir! Thanks! |
Sorry I meant to post the previous comment on #2315 but this issue can be closed too as openssl and tor builds have been succeeding. |
It looks like the way we're building OpenSSL for Tor broke again in the past week or so. When the script tries to produce a shared library, it gives all kinds of linker errors about missing asan symbols, such as:
{{{
Step #4: crypto/fips-dso-cryptlib.o: In function
OPENSSL_die': Step #4: /src/openssl/crypto/cryptlib.c:421: undefined reference to
__asan_handle_no_return'}}}
Has anybody else run into this kind of thing? The OpenSSL makefile and the hacky options that we pass to it are sufficiently complicated that I am not quite sure how to approach this myself.
The text was updated successfully, but these errors were encountered: