I am able to build V8 as a static library using the following args.gn
*V8 Version: 13.4.114.19, *but when trying to link the static libraray with 
a  shared libaray , this is failing with errors 

On Linux RHEL 8 
the args.gn used is 




















*v8_static_library = trueis_component_build = falseis_debug = 
falsetarget_cpu = "x64"use_custom_libcxx = falsev8_monolithic = 
truev8_use_external_startup_data = falseis_clang = 
falseclang_use_chrome_plugins = falsetreat_warnings_as_errors = 
falsev8_enable_fast_torque = falsev8_enable_sandbox = 
falsev8_enable_backtrace = falsev8_enable_disassembler = 
falsev8_enable_object_print = falsev8_enable_verify_heap = 
falsedcheck_always_on = falsev8_enable_i18n_support = falseuse_sysroot = 
falsev8_enable_webassembly = false*

but when tryign to link the static libarary with the shared libaray, it 
throws the followign error
r

*elease/libv8_monolith.a(api.o): relocation R_X86_64_TPOFF32 against symbol 
`_ZN2v88internal18g_current_isolate_E' can not be used when making a shared 
object; recompile with -fPIC/release/libv8_monolith.a(isolate.o): 
relocation R_X86_64_TPOFF32 against symbol 
`_ZN2v88internal21g_current_local_heap_E' can not be used when making a 
shared object; recompile with -fPIC*

and so on...this error is seen many times but with different .o files.

i used is_clang=true , i get the same errors.
also note that this was working earlier when the V8 libraries where shared 
libraires , but after moveing to static this issue is seen

can anyone share some pointers or a fix to resolve the issue.

regards
Pradish


-- 
-- 
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 visit 
https://groups.google.com/d/msgid/v8-users/c2e67732-514c-4391-89a2-7f7439948035n%40googlegroups.com.

Reply via email to