Package Base Details: anbox-git

Git Clone URL: (read-only)
Submitter: irtimmer
Maintainer: irtimmer
Last Packager: irtimmer
Votes: 109
Popularity: 2.940083
First Submitted: 2017-04-12 21:41
Last Updated: 2019-05-14 18:21

Pinned Comments

irtimmer commented on 2018-01-19 10:35

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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

Immanuel commented on 2019-06-13 14:02

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:

SBAPKat commented on 2019-06-13 08:01

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/ /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

simona commented on 2019-06-02 21:28

anbox: error while loading shared libraries: cannot open shared object file: No such file or directory

satcom886 commented on 2019-05-24 12:07

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

satcom886 commented on 2019-05-24 11:29

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

WhyNotHugo commented on 2019-05-22 07:50

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

diff --git a/PKGBUILD b/PKGBUILD
index b3196f9..52d29b5 100644
@@ -17,6 +17,7 @@ source=("git+"
+        ''
@@ -26,6 +27,7 @@ sha256sums=('SKIP'
+            'SKIP'

 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() {

amatwkgs commented on 2019-05-16 03:20

If you are using a kernel >= 5.1, please see for a possible fix.

zethex commented on 2019-05-15 09:40

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.

JJK commented on 2019-05-12 19:31

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'

HiJack88 commented on 2019-05-08 02:26

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.