[Lldb-commits] Build error in lldb

Zachary Turner via lldb-commits lldb-commits at lists.llvm.org
Thu Aug 6 09:56:26 PDT 2015


Resending to new mailing list.  @cs.uiuc.edu doesn't work anymore, all
messages should go to @lists.llvm.org.

On Thu, Aug 6, 2015 at 8:46 AM Zachary Turner <zturner at google.com> wrote:

> This patch (http://reviews.llvm.org/D11717) was supposed to fix it, but I
> don't see anything posted to lldb-commits indicating that it was actually
> committed.  Can you confirm if this patch exists in  your repo or not, and
> if not please try to apply this and let me know if it works.
>
> On Wed, Aug 5, 2015 at 11:48 PM Kallesh, Vijay-teekinavar <
> Vijay-teekinavar.Kallesh at amd.com> wrote:
>
>> Hi Zachary Turner,
>>
>>
>>
>> Below error was observed on lldb while compiling llvm on Red Hat
>> Enterprise Linux Server release 7.1,
>>
>>
>>
>> llvm[3]: Linking Release+Asserts Shared Library liblldb.so
>>
>> /home/amd/JENKINS/workspace/CPUPC_Mirror_Branch/2015-08-04_12-46-03/Release+Asserts/lib/liblldbAPI.a(SystemInitializerFull.o):
>> In function `lldb_private::SystemInitializerFull::InitializeSWIG()':
>>
>> SystemInitializerFull.cpp:(.text._ZN12lldb_private21SystemInitializerFull14InitializeSWIGEv+0x12d):
>> undefined reference to
>> `lldb_private::ScriptInterpreterPython::InitializeInterpreter(void (*)(),
>> bool (*)(char const*, char const*,
>> std::shared_ptr<lldb_private::StackFrame> const&,
>> std::shared_ptr<lldb_private::BreakpointLocation> const&), bool (*)(char
>> const*, char const*, std::shared_ptr<lldb_private::StackFrame> const&,
>> std::shared_ptr<lldb_private::Watchpoint> const&), bool (*)(char const*,
>> void*, lldb_private::SharingPtr<lldb_private::ValueObject> const&, void**,
>> std::shared_ptr<lldb_private::TypeSummaryOptions> const&, std::string&),
>> void* (*)(char const*, char const*,
>> lldb_private::SharingPtr<lldb_private::ValueObject> const&), void* (*)(char
>> const*, char const*, std::shared_ptr<lldb_private::Debugger>), unsigned
>> long (*)(void*), void* (*)(void*, unsigned int), int (*)(void*, char
>> const*), void* (*)(void*),
>> lldb_private::SharingPtr<lldb_private::ValueObject> (*)(void*), bool
>> (*)(void*), bool (*)(void*), void* (*)(void*), bool (*)(char const*, char
>> const*, std::shared_ptr<lldb_private::Debugger>&, char const*,
>> lldb_private::CommandReturnObject&,
>> std::shared_ptr<lldb_private::ExecutionContextRef>), bool (*)(void*,
>> std::shared_ptr<lldb_private::Debugger>&, char const*,
>> lldb_private::CommandReturnObject&,
>> std::shared_ptr<lldb_private::ExecutionContextRef>), bool (*)(char const*,
>> char const*, std::shared_ptr<lldb_private::Debugger>&), void* (*)(char
>> const*, char const*, std::shared_ptr<lldb_private::Process> const&), bool
>> (*)(char const*, char const*, std::shared_ptr<lldb_private::Process>&,
>> std::string&), bool (*)(char const*, char const*,
>> std::shared_ptr<lldb_private::Thread>&, std::string&), bool (*)(char
>> const*, char const*, std::shared_ptr<lldb_private::Target>&, std::string&),
>> bool (*)(char const*, char const*,
>> std::shared_ptr<lldb_private::StackFrame>&, std::string&), bool (*)(char
>> const*, char const*, lldb_private::SharingPtr<lldb_private::ValueObject>&,
>> std::string&), void* (*)(void*, char const*,
>> std::shared_ptr<lldb_private::Target> const&), void* (*)(char const*, char
>> const*, std::shared_ptr<lldb_private::ThreadPlan> const&), bool (*)(void*,
>> char const*, lldb_private::Event*, bool&))'
>>
>> /home/amd/JENKINS/workspace/CPUPC_Mirror_Branch/2015-08-04_12-46-03/Release+Asserts/lib/liblldbAPI.a(SystemInitializerFull.o):
>> In function `lldb_private::SystemInitializerFull::Initialize()':
>>
>> SystemInitializerFull.cpp:(.text._ZN12lldb_private21SystemInitializerFull10InitializeEv+0x12):
>> undefined reference to
>> `lldb_private::ScriptInterpreterNone::Initialize()'
>>
>> SystemInitializerFull.cpp:(.text._ZN12lldb_private21SystemInitializerFull10InitializeEv+0x17):
>> undefined reference to
>> `lldb_private::ScriptInterpreterPython::Initialize()'
>>
>> collect2: error: ld returned 1 exit status
>>
>>
>>
>> We see build is getting successfully built till git commit ID -
>> “e40914c1df4cfb4f93c9c7b6283707f9b6fa426c” and issue is on commit ID –
>> “fb2f0d0b20fd69f950bb8114e68b21c6f7fbb248”
>>
>>
>>
>> [amd at bglpence4 lldb]$ git log -2
>>
>> commit fb2f0d0b20fd69f950bb8114e68b21c6f7fbb248
>>
>> Author: Zachary Turner <zturner at google.com>
>>
>> Date:   Thu Jul 30 20:28:07 2015 +0000
>>
>>
>>
>>     Convert the ScriptInterpreter system to a plugin-based one.
>>
>>
>>
>>     Previously embedded interpreters were handled as ad-hoc source
>>
>>     files compiled into source/Interpreter.  This made it hard to
>>
>>     disable a specific interpreter, or to add support for other
>>
>>     interpreters and allow the developer to choose which interpreter(s)
>>
>>     were enabled for a particular build.
>>
>>
>>
>>     This patch converts script interpreters over to a plugin-based system.
>>
>>     Script interpreters now live in source/Plugins/ScriptInterpreter, and
>>
>>     the canonical LLDB interpreter, ScriptInterpreterPython, is moved
>> there
>>
>>     as well.
>>
>>
>>
>>     Any new code interfacing with the Python C API must live in this
>> location
>>
>>     from here on out.  Additionally, generic code should never need to
>>
>>     reference or make assumptions about the presence of a specific
>> interpreter
>>
>>     going forward.
>>
>>
>>
>>     Differential Revision: http://reviews.llvm.org/D11431
>>
>>     Reviewed By: Greg Clayton
>>
>>
>>
>>     git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@243681
>> 91177308-0d34-0410-b5e6-96231b3b80d8
>>
>>
>>
>> commit e40914c1df4cfb4f93c9c7b6283707f9b6fa426c
>>
>> Author: Chaoren Lin <chaorenl at google.com>
>>
>> Date:   Thu Jul 30 17:48:44 2015 +0000
>>
>>
>>
>>     Use only unnamed pipes to launch lldb-server gdbserver.
>>
>>
>>
>>     Summary:
>>
>>     If we used unnamed pipes instead of named pipes, we can avoid having
>> the
>>
>>     file system littered with debugserver-named-pipes if lldb-server
>> happens to
>>
>>     crash for whatever reason. Also, on some buggy systems, it's possible
>> to be
>>
>>     able to create but not to delete a fifo. Ideally, support for unnamed
>> pipes
>>
>>     should be added to debugserver as well, so we can avoid the `#ifdef`
>> here.
>>
>>
>>
>>     Reviewers: clayborg, vharron, chying
>>
>>
>>
>>     Subscribers: lldb-commits
>>
>>
>>
>>     Differential Revision: http://reviews.llvm.org/D11609
>>
>>
>>
>>     git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@243667
>> 91177308-0d34-0410-b5e6-96231b3b80d8
>>
>> [amd at bglpence4 lldb]$
>>
>>
>>
>> *Step followed:*
>>
>> ·        Git clone llvm
>>
>> ·        Git clone lldb under llvm/tools directory
>>
>> ·        mkdir BUILD_DIR
>>
>> ·        CONFIG_OPTIONS="--enable-optimized --enable-shared
>> --disable-debug-runtime --enable-libedit=no
>> --with-binutils-include=</home/amd/gold_linker/binutils/include>
>> --enable-targets=x86,x86_64 --prefix=$INSTALL_DIR"
>>
>> ·         cd BUILD_DIR
>>
>> ·        ../llvm/configure $CONFIG_OPTIONS
>>
>> ·        make
>>
>>
>>
>> Please let me know if I am missing anything here. If not, then kindly
>> help to fix the build error at earliest convenience.
>>
>>
>>
>>
>>
>> *VIJAY Kallesh*
>> [image: image001.png]
>>
>> *M :* +(91) 9886458185
>>
>> [image: image002.png]   facebook <https://www.facebook.com/AMD>  |
>> amd.com <http://www.amd.com/>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150806/7c6a561f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 339 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150806/7c6a561f/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 3857 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150806/7c6a561f/attachment-0003.png>


More information about the lldb-commits mailing list