LLVM Bugzilla is read-only and represents the historical archive of all LLVM issues filled before November 26, 2021. Use github to submit LLVM bugs

Bug 27237 - Cannot link lldb-server on a i386 system
Summary: Cannot link lldb-server on a i386 system
Status: RESOLVED WONTFIX
Alias: None
Product: lldb
Classification: Unclassified
Component: All Bugs (show other bugs)
Version: unspecified
Hardware: PC Linux
: P normal
Assignee: LLDB commit list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-06 04:24 PDT by Sylvestre Ledru
Modified: 2018-07-17 08:23 PDT (History)
3 users (show)

See Also:
Fixed By Commit(s):

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvestre Ledru 2016-04-06 04:24:25 PDT 
Looks like we are using too much memory during the link for a i386 system :

cd "/tmp/buildd/llvm-toolchain-snapshot-3.9~svn265476/build-llvm/tools/lldb/tools/lldb-server" && /tmp/cmake/bin/cmake -E cmake_symlink_executable ../../../../bin/lldb-server-3.9.0 ../../../../bin/lldb-server
make[4]: Leaving directory `/tmp/buildd/llvm-toolchain-snapshot-3.9~svn265476/build-llvm'
[ 98%] Built target lldb-server
/usr/bin/ld: final link failed: Memory exhausted
collect2: error: ld returned 1 exit status
make[4]: *** [lib/liblldb-3.9.so.1] Error 1
Comment 1 Rafael Ávila de Espíndola 2016-04-06 09:55:23 PDT 
I is trying to use more than 4gb of address space?
Comment 2 Sylvestre Ledru 2016-05-18 06:51:24 PDT 
I guess so.
Comment 3 Sylvestre Ledru 2016-07-02 15:43:49 PDT 
Adding -gsplit-dwarf to the CXXFLAGS fixes the issue.
Comment 4 labath 2018-07-17 08:20:54 PDT 
I don't think there is a real solution to this and -gsplit-dwarf is a viable workaround.
Comment 5 Sylvestre Ledru 2018-07-17 08:23:48 PDT 
Yeah, this is what I end up doing:
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/blob/snapshot/debian/rules#L51