I can repro. Looks like -fuse-ld=lld makes it work. Plain ld is probably missing some support. I'll update the docs.
On Mon, Nov 4, 2024 at 8:57 PM Justin Ferguson <jnfergu...@gmail.com> wrote: > Hello all, > > Thank you for the information about bug reporting. For posterity's > sake, because when I searched for the literals of my problem I found > zero relevant results: I filed a bug that can be found here: > https://issues.chromium.org/issues/377222400 > > Best Regards, > > Justin N. Ferguson > > On Mon, Nov 4, 2024 at 8:33 AM 'seth.b...@microsoft.com' via v8-dev > <v8-dev@googlegroups.com> wrote: > > > > Hi Justin, > > > > V8 bugs are tracked in the same site as Chromium bugs these days. When > creating an issue, start by selecting the component "Chromium > Blink > > JavaScript". The reporting template changes depending on the component you > select. > > > > Best, > > Seth > > > > On Sunday, November 3, 2024 at 12:12:24 PM UTC-8 Justin Ferguson wrote: > >> > >> Hello all, > >> > >> Does anyone happen to know the URL for the v8 bug reporting site? The > >> link I have is for chromium and when you go to file it only allows you > >> to select chromium versions as the affected software, so it seems > >> wrong and figured I'd check here before potentially filing in the > >> wrong place. > >> > >> As an aside, I also tried turning the thin archives of > >> libv8_libplatform.a and libv8_libbase.a into regular archive files > >> with no changes in outcome. > >> > >> Justin > >> > >> On Sat, Nov 2, 2024 at 12:34 PM Justin Ferguson <jnfer...@gmail.com> > wrote: > >> > > >> > 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 <jnfer...@gmail.com> > 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 v8-dev@googlegroups.com 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 v8-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3SPxCsvbbb6yuBGqm8AZjiVqKntbEZL3yvyjALv1iypFA%40mail.gmail.com.
