You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.
Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-kali7-amd64 all KERNEL_SRC=/lib/modules/5.16.0-kali7-amd64/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.16.0-kali7-amd64 (x86_64)
Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information.
Creating symlink /var/lib/dkms/anbox-binder/1/source -> /usr/src/anbox-binder-1
Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-kali7-amd64 all KERNEL_SRC=/lib/modules/5.16.0-kali7-amd64/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.16.0-kali7-amd64 (x86_64)
Consult /var/lib/dkms/anbox-binder/1/build/make.log for more information.
binder_linux 225280 0
ashmem_linux 20480 0
crw------- 1 root root 10, 123 Jul 10 06:28 /dev/ashmem
crw------- 1 root root 10, 122 Jul 10 06:28 /dev/binder`
If I try to install manually, everything goes right until I run dkms to process the packages, where I get this error
Building module:
cleaning build area...
make -j2 KERNELRELEASE=5.16.0-kali7-amd64 all KERNEL_SRC=/lib/modules/5.16.0-kali7-amd64/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.16.0-kali7-amd64 (x86_64)
Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information.`
Any ways around this??
Im running Kali GNU/Linux Rolling x86_64 with the 5.16.0-kali7-amd64
The text was updated successfully, but these errors were encountered:
INSTALL.sh outputs the following.
If I try to install manually, everything goes right until I run dkms to process the packages, where I get this error
Any ways around this??
Im running Kali GNU/Linux Rolling x86_64 with the 5.16.0-kali7-amd64
The text was updated successfully, but these errors were encountered: