Looks like a dependency issue in LLVM? Who was using this function? Why do we
need LLVMRuntimeDyld in lldb-server? We shouldn't have to use it. I know we
currently have some issues in lldb-server where it is pulling in too much
stuff, so we definitely don't want to include this just to fix a link issue.
lldb-server shouldn't require the LLDB expression parser AFAIK.
Does the link line mention who was wanting
llvm::RuntimeDyld::MemoryManager::anchor()?
> On Aug 28, 2017, at 9:42 AM, Peeter Joot via lldb-dev
> <lldb-dev@lists.llvm.org> wrote:
>
> I've built lldb in tree on Linux (RHEL 7.3) with a shared library
> configuration:
> CC=/usr/bin/clang CXX=/usr/bin/clang++ \
>
> cmake -G Ninja ../llvm \
> -DBUILD_SHARED_LIBS=true \
>
> ...
>
> The lldb-server binary does not link for me, as I get unresolved symbols
> including:
>
> llvm::RuntimeDyld::MemoryManager::anchor()
>
>
> I've worked around this by changing the link rules for lldb-server like so:
> diff --git a/tools/lldb-server/CMakeLists.txt
> b/tools/lldb-server/CMakeLists.txt
>
> index f8c57cb..35311a8 100644
>
> --- a/tools/lldb-server/CMakeLists.txt
>
> +++ b/tools/lldb-server/CMakeLists.txt
>
> @@ -82,6 +85,7 @@ add_lldb_tool(lldb-server INCLUDE_IN_FRAMEWORK
>
> lldbHost
>
> lldbInitialization
>
> lldbInterpreter
>
> + LLVMRuntimeDyld
>
> ${LLDB_PLUGINS}
>
> ${LLDB_SYSTEM_LIBS}
>
>
> Is this a known issue, and what would the proper fix for this look like?
>
> --
> Peeter
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
