I don't think it's because debian's libraries don't even agree with each other, from the link I posted before, It seems chromium's script specifically replaces some .so's dependency from libdbus-1.so.3 to libdbus-1.so.0 to workaround a lld's bug.Maybe chromium always use lld as linker, and did't test the ld linker? I'm not sure. Are you using clang as compiler and ld as linker? And which version chromium are you compiling?
> It's not arm64... why do you say that? It's because your first post said so: > I am instructing chromium's build to use linux:unbundle with buildroot's target sysroot for the target binaries. But in the spirit of reducing dependencies towards the build host as well as buildroot, I have opted to let chromium's build system use the > > the install-sysroot.py generated sysroots for* arm64* (build host) and i386 (v8 snapshots). This was just somewhat blindly following the advice of the error message to invoke install-sysroot --arch=*arm64* and i386. On Friday, February 26, 2021 at 9:45:22 AM UTC+8 [email protected] wrote: > Hi Z, > > Thanks for your answer, see inline... > > > On Feb 25, 2021, at 21:24, [email protected] < > [email protected]> wrote: > > > > Is it like: "warning: libdbus-1.so.0, needed by ../../build/linux/xxxx/ > libatk-bridge-2.0.so, not found (try using -rpath or -rpath-link)" and > there is a libdbus-1.so.3 in sysroot? > > Yes, exactly. except these files are all within debian_sid_i386-sysroot, > fetched and deflated by install-sysroot.py. So it's weird that the debian > sid libraries don't even agree with each other. > > > I have seen that error message when I cross compile for arm64 target and > set use_lld to false, I think it may be related with > https://chromium-review.googlesource.com/c/chromium/src/+/2220362. The > error is gone when I use lld linker, so . Hope it helps! > > I will look into this, but from what I can tell, these are binary artifact > made by debian and archived by chromium a while ago, I did not produce > these files... > > ``` > .../build/linux/debian_sid_i386-sysroot$ ~/find_libdbus_dependants.sh > ./usr/lib/i386-linux-gnu/libavahi-client.so.3 depends on libdbus-1.so.3 > ./usr/lib/i386-linux-gnu/libpulse.so.0 depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/pulseaudio/libpulsecommon-13.0.so depends on > libdbus-1.so.3 > ./usr/lib/i386-linux-gnu/libdbus-glib-1.so.2.3.4 depends on libdbus-1.so.3 > ./usr/lib/i386-linux-gnu/libgnome-keyring.so.0 depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libpulse.so.0.21.1 depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libgnome-keyring.so depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libavahi-client.so.3.2.9 depends on libdbus-1.so.3 > ./usr/lib/i386-linux-gnu/libatk-bridge-2.0.so depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libpulse.so depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libatk-bridge-2.0.so.0.0.0 depends on > libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libatspi.so depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libatk-bridge-2.0.so.0 depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libgnome-keyring.so.0.2.0 depends on > libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libatspi.so.0.0.1 depends on libdbus-1.so.0 > ./usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 depends on libdbus-1.so.3 > ./usr/lib/i386-linux-gnu/libatspi.so.0 depends on libdbus-1.so.0 > > .../build/linux/debian_sid_i386-sysroot$ find -name "libdbus-1.so.*" > ./lib/i386-linux-gnu/libdbus-1.so.3.19.11 > ./lib/i386-linux-gnu/libdbus-1.so.3 > ``` > > > Besides, are you cross compiling for arm(32 bit) on x86 machine? Why the > sysroot is arm64 instead of arm? > > It's not arm64... why do you say that? > > Cheers and thanks again for the help!! -- -- 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 on the web visit https://groups.google.com/d/msgid/v8-dev/eee03551-4d2c-449f-a352-4c0890855c00n%40googlegroups.com.
