After following up (I've been hitting my head against this for a week at least), and updating ubuntu to another version, I've managed to get it to link and run by forcing -lc++ against libc++-dev and libc++-helper
thanks Ben, you can stand down :) I appreciate the response, though. On Monday, February 12, 2018 at 12:58:17 PM UTC-8, Jerry Sievert wrote: > > also forgot to add that I'm using -std=c++11 on compile > > On Monday, February 12, 2018 at 12:57:33 PM UTC-8, Jerry Sievert wrote: >> >> 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/v8gen.py x64.release -- is_component_build=false >> v8_static_library=true v8_use_snapshot=true >> v8_use_external_startup_data=false >> ninja -C out.gn/x64.release d8 >> >> I dropped down to shell.cc 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../out.gn/x64.output/obj -L../ >> out.gn/x64.output/obj/third_party/icu -[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 >>> <je...@legitimatesounding.com> 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 shell.cc >>> > >>> > 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 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. For more options, visit https://groups.google.com/d/optout.
