[LLVMdev] "has different visibility" warnings

[Gordon Henriksen]

http://lists.cs.uiuc.edu/pipermail/llvmdev/2008-August/016763.html

On 2008-09-05, at 22:46, Talin wrote:

> Recently I started getting these warnings - thousands of them - and  
> I'm
> not sure what I did to cause them or how to solve them:
>
> ld: warning llvm::MemoryBuffer::getBufferStart() const has different
> visibility (1) in /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and
> (2) in /usr/local/lib/libLLVMSupport.a(CommandLine.o)
> ld: warning
> llvm::OwningPtr<llvm::MemoryBuffer>::OwningPtr(llvm::MemoryBuffer*)has
> different visibility (1) in
> /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and (2) in
> /usr/local/lib/libLLVMSupport.a(CommandLine.o)
> ld: warning
> llvm::OwningPtr<llvm::MemoryBuffer>::OwningPtr(llvm::MemoryBuffer*)has
> different visibility (1) in
> /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and (2) in
> /usr/local/lib/libLLVMSupport.a(CommandLine.o)
> ld: warning llvm::OwningPtr<llvm::MemoryBuffer>::~OwningPtr()has
> different visibility (1) in
> /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and (2) in
> /usr/local/lib/libLLVMSupport.a(CommandLine.o)
> ld: warning llvm::OwningPtr<llvm::MemoryBuffer>::~OwningPtr()has
> different visibility (1) in
> /usr/local/lib/libLLVMSupport.a(MemoryBuffer.o) and (2) in
> /usr/local/lib/libLLVMSupport.a(CommandLine.o)
> ld: warning llvm::APInt::isSingleWord() consthas different visibility
> (2) in /usr/local/lib/libLLVMTarget.a(TargetData.o) and (1) in
> /usr/local/lib/libLLVMSupport.a(APFloat.o)
> ld: warning llvm::APInt::isSingleWord() consthas different visibility
> (2) in /usr/local/lib/libLLVMCore.a(Instructions.o) and (1) in
> /usr/local/lib/libLLVMSupport.a(APFloat.o)
> ld: warning llvm::APInt::getNumWords() consthas different visibility  
> (2)
> in /usr/local/lib/libLLVMCore.a(Instructions.o) and (1) in
> /usr/local/lib/libLLVMSupport.a(APFloat.o)
> ld: warning llvm::APInt::clearUnusedBits()     has different  
> visibility
> (2) in /usr/local/lib/libLLVMCore.a(Instructions.o) and (1) in
> /usr/local/lib/libLLVMSupport.a(APFloat.o)
>
> (and so on...) Any suggestions?
>
> -- Talin
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev



— Gordon