I was suggesting what I believe to be the opposite from what you did. The
compiled v8 needs libc++ but you're building with libstdc++.
Try building your code with -stdlib=libc++ and see what happens.
This is just a guess, though.. if someone else has better info, do what
they say :)
On
I put libstdc++ in my library list, even try to link it statically but
nothing changes. Is there any way else to do it?
On Thursday, March 22, 2018 at 7:42:23 PM UTC-3, Zac Hansen wrote:
>
> I believe the std:: issues are from you linking v8 compiled with libc++
> against libstdc++.
>
> On
I took a look at the v8_shell Ninja script and it is compiled against dozen
of object files, not libraries. I will try to take all this files and make
a library using the "ar" and ranlib linux commands. Hope it works.
Any result I get, I post here, for sure, but I've wasted too much time
I believe the std:: issues are from you linking v8 compiled with libc++
against libstdc++.
On Thursday, March 22, 2018 at 3:37:50 PM UTC-7, Eduardo Bolis wrote:
>
> These are the first error lines (there are hundreds of them):
>
> g++ -o dist/Debug/GNU-Linux/teste-v8
These are the first error lines (there are hundreds of them):
g++ -o dist/Debug/GNU-Linux/teste-v8 build/Debug/GNU-Linux/main.o
-L/home/eduardo/workspace/v8-master/v8/out.gn/x64.release/obj
-L/home/eduardo/workspace/v8-master/v8/out.gn/x64.release/obj/third_party/icu
-lv8_base -lv8_libbase
