From the CFEBuildInstrs.html document:
Fix 2: If you are building the C++ front-end on a CPU we haven't tried
yet, you will probably have to edit the appropriate version of
atomicity.h under src/libstdc++-v3/config/cpu/name-of-cpu/atomicity.h
and apply a patch so that it does not use inline assembly.
Not sure if that's related or not.
Could you provide the bytecode file you're linking, the gccld command
line, and etc. so I can replicate this? It sounds like a bug.
Thanks,
Reid.
On Tue, 2004-12-21 at 07:50, Jeff Cohen wrote:> I'm getting a large number of failures with this error:
>
> gccld: error: Cannot link in module
> '/home/llvm-gcc/install/lib/libstdc++.a(ostream-inst.o)': Linking
> globals named '_ZN16__Atomicity_lockILi0EE17_S_atomicity_lockE':
symbol
> multiply defined!
> gccld: error: Cannot link archive
'/home/llvm-gcc/install/lib/libstdc++.a'
>
> Any simple solution? Or is this a bug?
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20041221/9165c7d4/attachment.sig>