From: Alexander Turenko <alexander.turenko@tarantool.org> To: Igor Munkin <imun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH v1] Block linker flag '--no-undefined' Date: Wed, 8 Jul 2020 22:22:00 +0300 [thread overview] Message-ID: <20200708192200.vwd7thsmsjurdtql@tkn_work_nb> (raw) In-Reply-To: <20200708113726.GH5559@tarantool.org> > Minor: I reworded the message a bit: > | Found that OpenSUSE toolchain adds '--no-undefined' linked flag leading Typo: linked -> linker. > Strictly saying, I see no reason to fix the problem here. These changes > are similar and one ought to add this "woodoo magic" line to every > CMakeLists.txt used for building dynamic libraries using Lua C API. > Since we are using <build_lualib> to build these extensions can you make > this change there? I missed this way. It should work, but we should care about not leaving a test/foo subdirectory scope. I think it should be verified manually. I would even add a comment regarding the macro behaviour: it affects current cmake variable scope and so a user should care to don't use it in a top level scope. Sadly, we cannot solve the problem with properties, because flags from the LINK_FLAGS target property are added before CMAKE_SHARED_LINKER_FLAGS flags and because there is no --no-undefined counterpart linker option (there is `--undefined foo` to allow certain symbols to be undefined, but is not what we need here). WBR, Alexander Turenko.
next prev parent reply other threads:[~2020-07-08 19:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-06 12:51 Alexander V. Tikhonov 2020-07-06 20:41 ` Alexander Turenko 2020-07-08 11:37 ` Igor Munkin 2020-07-08 14:25 ` Alexander V. Tikhonov 2020-07-08 19:22 ` Alexander Turenko [this message] 2020-07-09 5:41 ` Alexander V. Tikhonov 2020-07-09 19:14 ` Igor Munkin 2020-07-14 11:39 ` 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=20200708192200.vwd7thsmsjurdtql@tkn_work_nb \ --to=alexander.turenko@tarantool.org \ --cc=imun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v1] Block linker flag '\''--no-undefined'\''' \ /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