[cfe-dev] libc++ warning

[Nick Kledzik]

This is a bug in the externally shipping linker causing a spurious warning.  The generated dylib is fine.   You can ignore the warning.

-Nick
Apple Linker Engineer


On Nov 9, 2011, at 7:45 PM, Seth Cantrell wrote:
> Does anyone else see a bunch of warnings like the following when building libc++? I started seeing them a quite a while ago.
> 
>> ld: warning: direct access in __ZSt17__throw_bad_allocv to global weak symbol __ZTISt9bad_alloc means the weak symbol cannot be overridden at runtime. This was likely caused by different translation units being compiled with different visibility settings.
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev