[LLVMbugs] [Bug 8667] New: linking errors on FreeBSD-i386 with clang trunk
bugzilla-daemon at llvm.org
bugzilla-daemon at llvm.org
Mon Nov 22 18:19:51 PST 2010
http://llvm.org/bugs/show_bug.cgi?id=8667
Summary: linking errors on FreeBSD-i386 with clang trunk
Product: clang
Version: trunk
Platform: Other
OS/Version: FreeBSD
Status: NEW
Severity: normal
Priority: P
Component: LLVM Codegen
AssignedTo: unassignedclangbugs at nondot.org
ReportedBy: chromium at hybridsource.org
CC: llvmbugs at cs.uiuc.edu
I'm compiling Chromium on FreeBSD i386 and have had linking errors for the last
3 weeks when using clang trunk, though the same source links fine if I use
clang 2.8 on i386 or clang trunk on amd64. The problem started when I updated
to llvm-117848/clang-117842 and persists up to clang 119910 today. These are
the two linker errors that I keep hitting now with the system GNU linker:
/usr/bin/ld:
out/Release/obj.host/ssl_false_start_blacklist_process/net/base/ssl_false_start_blacklist_process.o(.text.main+0x886):
unresolvable relocation against symbol
`_ZNSs4_Rep20_S_empty_rep_storageE@@GLIBCXX_3.4'
/usr/bin/ld:
out/Release/obj.host/protoc/third_party/protobuf/src/google/protobuf/compiler/code_generator.o(.text._ZN6google8protobuf8compiler23ParseGeneratorParameterERKSsPSt6vectorISt4pairISsSsESaIS6_EE+0xd1):
unresolvable relocation against symbol
`_ZNSs4_Rep20_S_empty_rep_storageE@@GLIBCXX_3.4'
Rafael asked me if integrated-as made a difference so I just tried it and it
made no difference if it was turned on or off: I usually compile with
integrated-as turned off. I took a look at that symbol in the object files and
nothing stood out for me, between the objects generated by clang 2.8 and trunk.
rjmccall asked for the command line and preprocessed source so I'm attaching
those.
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the llvm-bugs
mailing list