From: Sergey Kaplun <skaplun@tarantool.org> To: Igor Munkin <imun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org, Alexander Turenko <alexander.turenko@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH 2/2] msgpack: fix wrong mp_ext type in error message Date: Wed, 15 Jul 2020 18:21:36 +0300 [thread overview] Message-ID: <20200715152136.GA13607@root> (raw) In-Reply-To: <20200715093215.GA947@root> On 15.07.20, Sergey Kaplun wrote: > Hi Igor! Thanks for the review! <snipped> > > > +target_link_libraries(mplua.test unit box server core > > > + ${CURL_LIBRARIES} ${LIBYAML_LIBRARIES} ${READLINE_LIBRARIES} > > > + ${ICU_LIBRARIES} ${LUAJIT_LIBRARIES}) > > > > Why should this be done in such complex way? Do your test binary need > > *all* mentioned libs? I see no usage for libcurl, libreadline, libicu, > > libyaml in the test. Furthermore, IIRC LuaJIT symbols are provided by > > libserver archive. > > When I had tried to build my test I found out that lua/msgpack.c requires build > with tarantool_lua_ibuf (from lua/utils.c). > > | /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: > | CMakeFiles/mplua.test.dir/__/__/src/lua/msgpack.c.o: in function > | `lua_msgpack_encode': msgpack.c:(.text+0x1673): undefined reference to > | `tarantool_lua_ibuf' > > Building utils requires build with httpc_lua (from lua/httpc.c). And it > requires curl library. > > | /usr/lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-linux-gnu/bin/ld: > | CMakeFiles/mplua.test.dir/__/__/src/lua/init.c.o:(.data.rel+0x1b8): undefined > | reference to `httpc_lua' > > And so on. I suppose that building with libserver and its linkage with > necessary libraries would be less bulky than list all necessary sources > inside add_executable. It would be nice if you will offer a prettier > approach. > > Unfortunately libserver doesn't provides necessary symbols, but requires it to > be built. > | nm -g src/libserver.a | grep lua_type | sort | uniq > | U lua_type > | U lua_typename > > > > > Well, I faced the following linkage error when the test is build in > > Release mode: > > | [ 87%] Linking CXX executable mplua.test > > | /usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: ../../src/libcore.a(evio.cc.o): in function `evio_service_bind(evio_service*, char const*)': > > | evio.cc:(.text+0x9e2): undefined reference to `uri_parse' > > | collect2: error: ld returned 1 exit status > > Hmm, I build successfully with Debug/RelWithDebInfo/Release mode > locally. How did you get this error? Did you build from my branch or > applied diff to master? I can offer something like that: | target_link_libraries(mplua.test server box core unit) > > > diff --git a/test/unit/mplua.c b/test/unit/mplua.c <snipped> > > [1]: https://github.com/tarantool/tarantool/issues/5017 > [2]: https://github.com/msgpack/msgpack/blob/master/spec.md#ext-format-family > > -- > Best regards, > Sergey Kaplun -- Best regards, Sergey Kaplun
next prev parent reply other threads:[~2020-07-15 15:21 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-15 15:56 [Tarantool-patches] [PATCH 0/2] Msgpack wrong extension " Sergey Kaplun 2020-06-15 15:56 ` [Tarantool-patches] [PATCH 1/2] lib: update msgpuck library Sergey Kaplun 2020-06-15 15:56 ` [Tarantool-patches] [PATCH 2/2] msgpack: fix wrong mp_ext type in error message Sergey Kaplun 2020-07-14 15:46 ` Igor Munkin 2020-07-15 9:32 ` Sergey Kaplun 2020-07-15 15:21 ` Sergey Kaplun [this message] 2020-07-16 20:53 ` Igor Munkin 2020-07-17 8:35 ` Sergey Kaplun 2020-07-17 9:09 ` Alexander Turenko 2020-07-17 9:54 ` Sergey Kaplun 2020-07-17 9:23 ` sergos 2020-07-17 10:12 ` Igor Munkin 2020-07-17 11:02 ` Sergey Kaplun 2020-07-17 11:27 ` [Tarantool-patches] [PATCH 0/2] Msgpack wrong extension " Kirill Yukhin
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=20200715152136.GA13607@root \ --to=skaplun@tarantool.org \ --cc=alexander.turenko@tarantool.org \ --cc=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 2/2] msgpack: fix wrong mp_ext type in error message' \ /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