Thanks Ben,

That's what I had been thinking as well, and moved to clang++-5.0 with 
llvm's libc++ as well.

libv8 is being built via:

tools/dev/ x64.release -- is_component_build=false 
v8_static_library=true v8_use_snapshot=true 
ninja -C d8

I dropped down to to try to debug the issue (thus taking any of 
the code I'm maintaining, plv8, out of the loop):

g++ -I.. -I../include -L../ 
-L../ -[allofthelibs that are needed 
that also work on macOS]

On Monday, February 12, 2018 at 12:52:08 PM UTC-8, Ben Noordhuis wrote:
> On Mon, Feb 12, 2018 at 9:29 PM, Jerry Sievert 
> < <javascript:>> wrote: 
> > Hello, 
> > 
> > Apologies if this is the wrong place to post - I've also searched, and 
> have 
> > been unable to find an answer. 
> > 
> > I've been attempting to link to v8, with an environment that has worked 
> fine 
> > in the past with older versions of v8 (make native, as opposed to 
> ninja). 
> > I've updated for any API changes, and have everything working well under 
> > macOS, but am having issues during the link phase on Linux: 
> > 
> > std::__1::__shared_weak_count::~__shared_weak_count() 
> > 
> > is missing after link, when I attempt to do any execution.  I'm having 
> the 
> > same issue even compiling 
> > 
> > I'm hoping I'm just missing something at the linker step (using g++ as 
> the 
> > linker passthrough). 
> > 
> > Any help would be appreciated! 
> That link error suggests you built V8 against llvm's libc++ but are 
> now trying to link it against GNU's libstdc++.  What are the exact 
> steps you used to build libv8 and the shell executable?  Can you 
> include build output? 

v8-users mailing list
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 
For more options, visit

Reply via email to