Toby1009 commented on issue #245:
URL: 
https://github.com/apache/incubator-resilientdb/issues/245#issuecomment-5066561811

   Hi @DimitriBelikov, I ran into the same failures you reported and traced them
   down. The fix is up in #264 — it covers the arm64 Bazel installation failure
   (the Bazel apt repo is amd64-only and the source-build fallback also breaks 
on
   newer GCC), the GCC 13+ compile errors in the vendored dependencies, and a
   client-tool hang that only shows up on arm64. The PR description has the full
   analysis and a verification matrix covering Ubuntu 22.04, 24.04 and 26.04 on
   arm64, plus 24.04 on amd64.
   
   If you have a chance, it would help a lot if you could try it on the setup
   where you first hit this:
   
       docker run --rm -it --platform linux/arm64 ubuntu:24.04 bash
       apt-get update && apt-get install -y sudo curl git
       git clone -b fix/install-sh-arm64 
https://github.com/Toby1009/incubator-resilientdb
       cd incubator-resilientdb
       ./INSTALL.sh
       bazel build //service/kv:kv_service
   
   Two things worth knowing before you start:
   
   - The build takes around 10 minutes on arm64 and spends most of it on two
     actions (`cryptopp`, then `Compiling duckdb.cpp`). It looks stalled but is
     not.
   - Please build `//service/kv:kv_service` rather than `...`. A full-tree build
     still fails on current Ubuntu for an unrelated reason — pybind11 2.6.2 does
     not compile against Python 3.11+ — which is tracked separately in #262 and
     is out of scope here.
   
   A confirmation — or anything still broken on your machine — would be great to
   have on record before the PR is reviewed.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to