From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: tarantool-patches@freelists.org,
"Alexander V. Tikhonov" <avtikhon@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v1] Fix static build
Date: Thu, 13 Jun 2019 12:47:36 +0300 [thread overview]
Message-ID: <20190613094736.k4oirzo45jvqnj7b@tkn_work_nb> (raw)
In-Reply-To: <20190613081901.vowzuh45oyzpvwzr@tarantool.org>
On Thu, Jun 13, 2019 at 11:19:01AM +0300, Kirill Yukhin wrote:
> Hello,
>
> On 07 Jun 06:55, Alexander V. Tikhonov wrote:
> > Added to cmake environment CMAKE_DL_LIBS (The name of the library
> > that has dlopen and dlclose in it, usually -ldl) to openssl build
> > to add DL library, to fix the following fails:
> >
> > Linking CXX executable crypto.test
> > /usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_globallookup':
> > dso_dlfcn.c:(.text+0x11): undefined reference to `dlopen'
> > dso_dlfcn.c:(.text+0x24): undefined reference to `dlsym'
> > dso_dlfcn.c:(.text+0x2f): undefined reference to `dlclose'
> > /usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_bind_func':
> > dso_dlfcn.c:(.text+0x334): undefined reference to `dlsym'
> > dso_dlfcn.c:(.text+0x3f2): undefined reference to `dlerror'
> > /usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_load':
> > dso_dlfcn.c:(.text+0x459): undefined reference to `dlopen'
> > dso_dlfcn.c:(.text+0x4c9): undefined reference to `dlclose'
> > dso_dlfcn.c:(.text+0x502): undefined reference to `dlerror'
> > /usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_pathbyaddr':
> > dso_dlfcn.c:(.text+0x5a1): undefined reference to `dladdr'
> > dso_dlfcn.c:(.text+0x601): undefined reference to `dlerror'
> > /usr/local/lib64/libcrypto.a(dso_dlfcn.o): In function `dlfcn_unload':
> > dso_dlfcn.c:(.text+0x662): undefined reference to `dlclose'
> > collect2: error: ld returned 1 exit status
> > make[2]: *** [test/unit/crypto.test] Error 1
> > make[1]: *** [test/unit/CMakeFiles/crypto.test.dir/all] Error 2
> >
> > Closes #4245
>
> I've checked your patch into 2.1 and master.
I think we should fix static build on 1.10 too.
WBR, Alexander Turenko.
prev parent reply other threads:[~2019-06-13 9:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 13:20 [tarantool-patches] " Alexander V. Tikhonov
2019-06-10 7:48 ` [tarantool-patches] " Alexander Turenko
2019-06-13 8:19 ` Kirill Yukhin
2019-06-13 9:47 ` Alexander Turenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190613094736.k4oirzo45jvqnj7b@tkn_work_nb \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH v1] Fix static build' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox