Hi, Following up with what I said about the build hanging when I omit the libv8_libplatform.a and libv8_libbase.a. It takes a long time and hangs but eventually turns up:
$ g++ -m64 -I. -Iinclude samples/hello-world.cc -o hello_world -fno-rtti -lv8_monolith -ldl -Lout.gn/x64.release.sample/obj/ -pthread -std=c++20 -DV8_COMPRESS_POINTERS -DV8_ENABLE_SANDBOX /usr/bin/ld: unknown architecture of input file `out.gn/x64.release.sample/obj//libv8_monolith.a(default-platform.o)' is incompatible with i386:x86-64 output /usr/bin/ld: unknown architecture of input file `out.gn/x64.release.sample/obj//libv8_monolith.a(default-thread-isolated-allocator.o)' is incompatible with i386:x86-64 output [...] /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(default-platform.o)(.eh_frame); no .eh_frame_hdr table will be created /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(default-thread-isolated-allocator.o)(.eh_frame); no .eh_frame_hdr table will be created /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(default-worker-threads-task-runner.o)(.eh_frame); no .eh_frame_hdr table will be created /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(delayed-task-queue.o)(.eh_frame); no .eh_frame_hdr table will be created /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(tracing-controller.o)(.eh_frame); no .eh_frame_hdr table will be created /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(api.o)(.eh_frame); no .eh_frame_hdr table will be created [...] /usr/bin/ld: error in out.gn/x64.release.sample/obj//libv8_monolith.a(memory-lowering.o)(.eh_frame); no .eh_frame_hdr table will be created collect2: error: ld returned 1 exit status $ I'm probably going to file a bug and escalate there, its a brand new fresh linux system and this is consistently happening, seems like it would affect everyone on the same platform. On Sat, Nov 2, 2024 at 11:42 AM Justin Ferguson <[email protected]> wrote: > > Hi, > > > > Long shot but, since you're linking to libv8_monolith.a anyway, why > > not drop libv8_libbase from the arguments? > > I get the same thing as with it: > > $ g++ -m64 -I. -Iinclude samples/hello-world.cc -o hello_world > -fno-rtti -lv8_monolith -ldl -Lout.gn/x64.release.sample/obj/ -pthread > -std=c++20 -DV8_COMPRESS_POINTERS -DV8_ENABLE_SANDBOX > /usr/bin/ld: unknown architecture of input file > `out.gn/x64.release.sample/obj//libv8_monolith.a(default-platform.o)' > is incompatible with i386:x86-64 output > /usr/bin/ld: unknown architecture of input file > `out.gn/x64.release.sample/obj//libv8_monolith.a(default-thread-isolated-allocator.o)' > is incompatible with i386:x86-64 output > /usr/bin/ld: unknown architecture of input file > `out.gn/x64.release.sample/obj//libv8_monolith.a(default-worker-threads-task-runner.o)' > is incompatible with i386:x86-64 output > [...] > > I should note that whenever I omit either of the library directives > and I get these screens full of errors from ld that the build process > hangs. I'm going to leave it and see what its final conclusion is, but > I think the build is broken-- this is a fresh linux install with all > of the instructions followed and the only thing done on the box was > build v8. > > Justin -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CADCX%2B3W70QHXeEadYxgLFfqrfVZZ619SpAbcAFVc5-DgNmR1EQ%40mail.gmail.com.
