Thank you, did the trick. Config haproxy backend server to use SSL like "server s1 s1.local:1000 ssl" will cause segment fault.
boringssl/crypto/digest/digest.c:98: EVP_MD_CTX_cleanup: Assertion `ctx->pctx == ((void *)0) || ctx->pctx_ops != ((void *)0)' failed. Aborted On Tue, Feb 7, 2017 at 11:17 PM, Emmanuel Hocdet <m...@gandi.net> wrote: > you need: > ADDLIB="-lpthread -ldecrepit" > > Le 7 févr. 2017 à 16:09, Igor Pav <i...@fastsp.net> a écrit : > > Hi, Emmanuel. build with static lib, but no luck, can you provide some > building details? Thanks. > > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_MUTEX_init': > /root/boringssl/crypto/thread_pthread.c:31: undefined reference to > `pthread_rwlock_init' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_MUTEX_lock_read': > /root/boringssl/crypto/thread_pthread.c:37: undefined reference to > `pthread_rwlock_rdlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_MUTEX_lock_write': > /root/boringssl/crypto/thread_pthread.c:43: undefined reference to > `pthread_rwlock_wrlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_MUTEX_unlock_read': > /root/boringssl/crypto/thread_pthread.c:49: undefined reference to > `pthread_rwlock_unlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_MUTEX_unlock_write': > /root/boringssl/crypto/thread_pthread.c:55: undefined reference to > `pthread_rwlock_unlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_MUTEX_cleanup': > /root/boringssl/crypto/thread_pthread.c:61: undefined reference to > `pthread_rwlock_destroy' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_STATIC_MUTEX_lock_read': > /root/boringssl/crypto/thread_pthread.c:65: undefined reference to > `pthread_rwlock_rdlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_STATIC_MUTEX_lock_write': > /root/boringssl/crypto/thread_pthread.c:71: undefined reference to > `pthread_rwlock_wrlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_STATIC_MUTEX_unlock_read': > /root/boringssl/crypto/thread_pthread.c:77: undefined reference to > `pthread_rwlock_unlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_STATIC_MUTEX_unlock_write': > /root/boringssl/crypto/thread_pthread.c:83: undefined reference to > `pthread_rwlock_unlock' > /build/slib/libcrypto.a(thread_pthread.c.o): In function `CRYPTO_once': > /root/boringssl/crypto/thread_pthread.c:89: undefined reference to > `pthread_once' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `thread_local_init': > /root/boringssl/crypto/thread_pthread.c:126: undefined reference to > `pthread_key_create' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_get_thread_local': > /root/boringssl/crypto/thread_pthread.c:135: undefined reference to > `pthread_getspecific' > /build/slib/libcrypto.a(thread_pthread.c.o): In function > `CRYPTO_set_thread_local': > /root/boringssl/crypto/thread_pthread.c:150: undefined reference to > `pthread_getspecific' > /root/boringssl/crypto/thread_pthread.c:158: undefined reference to > `pthread_setspecific' > collect2: error: ld returned 1 exit status > make: *** [haproxy] Error 1 > > On Tue, Feb 7, 2017 at 9:12 PM, Emmanuel Hocdet <m...@gandi.net> wrote: > > I Igor, > I build haproxy with boringssl static library to avoid any conflict with > openssl shared lib. > It also need to be link with libdecrepit (boringssl). > > Le 30 janv. 2017 à 14:28, Igor Pav <i...@fastsp.net> a écrit : > > sorry for unclear question, it's quite simple, build haproxy from git > with boringssl (DBUILD_SHARED_LIBS=1), just config a simple SSL > frontend. > > On Mon, Jan 30, 2017 at 5:42 PM, Willy Tarreau <w...@1wt.eu> wrote: > > On Mon, Jan 30, 2017 at 04:07:33PM +0800, Igor Pav wrote: > > any idea with error? > > undefined symbol: BIO_read_filename > > > I doubt you'll get any useful response if you don't provide at least a > bit of information, such as what ssl lib you're using, whether or not > this is with the patch applied, build options maybe, etc... > > Willy > > > > >
