Instead of hunting down the issue I set:
v8_enable_webassembly=false
That got rid of the above undefined symbol issues. If you need WASM then I
think it is something generating libc++ specific code (ie:
std::__Cr::atomic) since the MS c++ lib doesn't use "__Cr" namespace.
Not 100% sure of this
Chris
I myself gave up on DLL version many years ago after many further years of
significant pain. The DLL configuration is consistently broken. The team is
very responsive, and problems are fixed quickly, but something else quickly
breaks soon after. I migrated to the "monolith" build, and I isola
Hi Chris,
i observe the same problem now for a while and did not manage to solve it.
But what i observed: The 'monolith' configuration (
*is_component_build=false*) works.
Chris Hillery schrieb am Freitag, 19. Januar 2024 um 12:50:06 UTC+1:
> I should mention that I've tried building v8 12.1.285.
I should mention that I've tried building v8 12.1.285.26; 12.2.247; as well
as whatever "fetch v8" brings me, all with the same error. However in the
past, I've built v8 11.6.189.8 with the same gn configuration options
successfully.
Ceej
aka Chris Hillery
On Friday, January 19, 2024 at 3:46:0
