Turns out I was missing a dependency from my executable to libc++ and so `_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS` wasn't propagated to the compile definitions.
On Thursday, 2 November 2023 at 16:02:01 UTC+1 Kasper Isager Dalsgarð wrote: > Hi! > > I'm seeing linker warnings and errors related to libc++ symbols when > linking to a monolithic V8 build made using the in-tree libc++, i.e. > `using_custom_libcxx = true`, on Windows. On both macOS and Linux I'm not > seeing any issues and my executables are linked correctly. > > Specifically, I'm seeing warnings like these... > > ``` > lld-link : warning : <path>: locally defined symbol imported: public: > void __cdecl std::__Cr::__shared_weak_count::__release_weak(void) (defined > in v8.lib(memory.obj)) > ``` > > ...and errors like these: > > ``` > lld-link : error : undefined symbol: __declspec(dllimport) public: void > __cdecl std::__Cr::__shared_count::__add_shared(void) > ``` > > Looking through the object library using `dumpbin /symbols` I'm indeed not > seeing any of the symbols that the linker complains are missing so that > part makes sense. There are a lot of `std::__Cr::*` symbols present though, > so some of them make their way into the object library. > > Any ideas on how I might solve this? > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-users/ea20fbdd-d4d5-4cbc-a8a7-33c000e76a50n%40googlegroups.com.
