Same problem here. I build v8_monolith.a but inside for example api.o : objdump -f api.o objdump: api.o: unknown type [0x40000014] section `.crel.text'
api.o: file format elf64-little architecture: UNKNOWN!, flags 0x00000010: HAS_SYMS start address 0x0000000000000000 El martes, 27 de mayo de 2025 a las 14:49:45 UTC-3, tae...@gmail.com escribió: > I built v8 with the following args.gn options and when I ran 'objdump -f' > for output library files, I am seeing 'unknown type' and 'architecture: > unknowm' issues with them(They should be x64). So, I could not use them to > link to my application due to link error. My application was built with > gcc-toolset-12. Anyone knows how to fix this issue? I guess these library > files are 'thin archive' and if that's the issue, how can I build for > 'thick archive' ? Any advice would be appreciated. > > Thanks, > TK > > > ------- args.gn ------ > v8_static_library = true > is_component_build = false > is_debug = false > target_cpu = "x64" > use_custom_libcxx = false > v8_monolithic = true > v8_monolithic_for_shared_library = true > v8_use_external_startup_data = false > is_clang = true > clang_use_chrome_plugins = false > treat_warnings_as_errors = false > v8_enable_fast_torque = false > v8_enable_sandbox = false > v8_enable_backtrace = false > v8_enable_disassembler = false > v8_enable_object_print = false > v8_enable_verify_heap = false > dcheck_always_on = false > use_sysroot = false > v8_enable_webassembly = false > v8_enable_i18n_support = true > icu_use_data_file = false > > -------------- unknow type issues ------------------- > *objdump -f out/release/obj/libv8_libbase.a | more* > objdump: out/release/obj/v8_libbase/bits.o: unknown type [0x40000014] > section `.crel.eh_frame' > In archive out/release/obj/libv8_libbase.a: > > out/release/obj/v8_libbase/abort-mode.o: file format elf64-x86-64 > architecture: i386:x86-64, flags 0x00000010: > HAS_SYMS > start address 0x0000000000000000 > > objdump: out/release/obj/v8_libbase/bounded-page-allocator.o > : *unknown type* [0x40000014] section `out/release/obj/v8_libbase/bits.o: > file format elf64-little > .crel.text'*architecture: UNKNOWN*!, flags 0x00000010: > > HAS_SYMS > start address 0x0000000000000000 > > objdump: > out/release/obj/v8_libbase/cpu.o: *unknown type > *[out/release/obj/v8_libbase/bounded-page-allocator.o: > file format elf64-little > 0x40000014] section `*architecture: UNKNOWN*!, flags 0x00000010: > .crel.textHAS_SYMS > ' > start address 0x0000000000000000 > > objdump: out/release/obj/v8_libbase/stack_trace.o: unknown type [ > 0x40000014] section `.crel.textout/release/obj/v8_libbase/cpu.o: file > format elf64-little > 'architecture: UNKNOWN!, flags 0x00000010: > > HAS_SYMS > start address 0x0000000000000000 > > objdump: > out/release/obj/v8_libbase/division-by-constant.o: unknown type > [out/release/obj/v8_libbase/stack_trace.o: file format elf64-little > 0x40000014] section `architecture: UNKNOWN!, flags 0x00000010: > .crel.text'HAS_SYMS > -- -- 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/f4682aa9-bb2e-4707-b317-8bb828a03089n%40googlegroups.com.
