> On Feb 25, 2021, at 23:16, [email protected]
> <[email protected]> wrote:
>
> 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?
Yeah, I haven't had time yet to go into the issue you pointed out in detail...
I will. I just wanted to get this reply out quick.
I'm using a buildroot built llvm 11.0.1 ld.lld for the linker (well, and
compiler) and chromium version 87.0.4280.88
>
> > 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.
Oh wow, what a nice brain fart! I meant to write --arch=amd64!! The build host
is just a regular x86_64 machine. Duh! Sorry!!
--
--
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/FE1D8B51-E686-47F4-8E93-643ADEF0A3E6%40gmail.com.
