Arch Linux User Repository

WARNING: Before you go ahead and install Anbox on your system, please keep in mind that Anbox is not yet stable. Not every feature is working well yet. You will find bugs, see crashes and unexpected problems. As this is a Git package, patches should go upstream as they will not be bundled with the package.

There is already an issue on Github for the build error error: missing field 'features' initializer etc. I have filed a pull request with a small patch to fix that problem. See the issue here: https://github.com/anbox/anbox/issues/1153

binder module doesnt build, here's the makelog:

DKMS make.log for anbox-modules-binder-r1096.ea2b7a3 for kernel 5.1.8-arch1-1-ARCH (x86_64) jeu. juin 13 09:21:02 CEST 2019 make -C /lib/modules/5.1.8-arch1-1-ARCH/build V=0 M=$PWD make[1] : on entre dans le répertoire « /usr/lib/modules/5.1.8-arch1-1-ARCH/build » CC [M] /var/lib/dkms/anbox-modules-binder/r1096.ea2b7a3/build/binder.o CC [M] /var/lib/dkms/anbox-modules-binder/r1096.ea2b7a3/build/deps.o /var/lib/dkms/anbox-modules-binder/r1096.ea2b7a3/build/binder.c:3406:11: error: initialisation de « vm_fault_t ()(struct vm_fault ) » {alias « unsigned int ()(struct vm_fault ) »} depuis le type pointeur « int ()(struct vm_fault ) » qui est incompatible [-Werror=incompatible-pointer-types] .fault = binder_vm_fault, ^~~~~~~~~~~~~~~ /var/lib/dkms/anbox-modules-binder/r1096.ea2b7a3/build/binder.c:3406:11: note: (près de l'initialisation de « binder_vm_ops.fault ») cc1 : certains avertissements sont traités comme des erreurs make[2]: [scripts/Makefile.build:275: /var/lib/dkms/anbox-modules-binder/r1096.ea2b7a3/build/binder.o] Error 1 make[1]: [Makefile:1571: module/var/lib/dkms/anbox-modules-binder/r1096.ea2b7a3/build] Error 2 make[1] : on quitte le répertoire « /usr/lib/modules/5.1.8-arch1-1-ARCH/build » make: *** [Makefile:8: all] Error 2

anbox: error while loading shared libraries: libprotobuf-lite.so.17: cannot open shared object file: No such file or directory

I can confirm, that the modifications provided by @WhyNotHugo work. The package builds successfully and the module works.

Please update the PKGBUILD, so it works with 5.1.x kernels. It seems binder_linux does not build.

Apply this patch to PKGBUILD for this to build under the latest kernel:

diff --git a/PKGBUILD b/PKGBUILD
index b3196f9..52d29b5 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -17,6 +17,7 @@ source=("git+https://github.com/anbox/anbox.git"
        'anbox.conf'
        'anbox.desktop'
        'anbox-bridge.network'
+        'https://github.com/anbox/anbox-modules/pull/19.patch'
        'anbox-bridge.netdev')
 sha256sums=('SKIP'
             'SKIP'
@@ -26,6 +27,7 @@ sha256sums=('SKIP'
             '3e07dc524a827c1651857cce28a06c1565bc5188101c140ed213bbafedc5abff'
             '7332d09865be553a259a53819cebddd21f661c7a251d78c2f46acd75c66676b6'
             '44899328725667041e6e84912da81c1d0147b708006eb2c2bb6503f271629ff0'
+            'SKIP'
             '559190df4d6d595480b30d8b13b862081fc4aac52790e33eb24cf7fbcb8003b8')

 pkgver() {
@@ -42,6 +44,9 @@ prepare() {
   # Don't build tests
   truncate -s 0 cmake/FindGMock.cmake
   truncate -s 0 tests/CMakeLists.txt
+
+  cd "$srcdir/anbox-modules"
+  patch -p0 binder/binder.c < ../19.patch
 }

 build() {

If you are using a kernel >= 5.1, please see https://github.com/anbox/anbox-modules/pull/19 for a possible fix.

Cannot find kernel modules after installing. Modprobe outputs that it cannot find the modules "binder_linux" and "ashmem_linux". On next boot systemd shows failed "Load Kernel Modules". Most likely because it also cannot find the modules.

For some reason after installing, ashmem is working, while binder is not working.

 ls -l /dev/{ashmem,binder}
ls: cannot access '/dev/binder': No such file or directory
crw-rw-rw- 1 root root 10, 56 May 12 21:11 /dev/ashmem

systemd-modules-load[281]: Inserted module 'ashmem_linux'
systemd-modules-load[281]: Failed to find module 'binder_linux'

I can answer yochananmarqos back on this. gmock & libdwarf are not needed in order to build the package here.

montefuscolo's proposal made the package compiling fine on my build system again, so that should be enough of a PKGBUILD update.