GithubHelp home page GithubHelp logo

ryanfortner / box64-debs Goto Github PK

View Code? Open in Web Editor NEW
59.0 4.0 9.0 28.54 GB

box64 debian/apt repository

Home Page: https://ryanfortner.github.io/box64-debs/

Shell 100.00%
debian box64 arm raspberrypi deb repository

box64-debs's Introduction

box64-debs

This is a simple Debian repository for the box64 project. New versions are compiled every 24 hours if a new commit on the master repository has been made.

These debs have been compiled using various target CPUs and systems. You can see all the available pkgs below.

All packages built on Ubuntu Focal and are compatible with gcc-9 and higher.

Repository installation

Involves adding .list file and gpg key for added security. Most users will just need the generic arm64 package, box64, but please see the package list below if you have a specifically supported system (Raspberry Pi, ROCKchip, etc...)

sudo wget https://ryanfortner.github.io/box64-debs/box64.list -O /etc/apt/sources.list.d/box64.list
wget -qO- https://ryanfortner.github.io/box64-debs/KEY.gpg | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/box64-debs-archive-keyring.gpg 
sudo apt update && sudo apt install box64 -y

If you don't want to add this apt repository to your system, you can download and install the latest arm64 deb from here.

CN mirror installation (click to expand)

Only for users in CN areas where GitHub is blocked. Disclaimer: I do not run this, use at your own risk

sudo wget https://cdn05042023.gitlink.org.cn/shenmo7192/box64-debs/raw/branch/master/box64-CN.list -O /etc/apt/sources.list.d/box64.list
wget -qO- https://cdn05042023.gitlink.org.cn/shenmo7192/box64-debs/raw/branch/master/KEY.gpg | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/box64-debs-archive-keyring.gpg 
sudo apt update

Alternatively, download the latest arm64 deb from here.

Package List

Package Name Notes Install Command
box64 Box64 built for generic ARM 64-bit systems. Older builds for this target were under box64-generic-arm or box64-arm64. sudo apt install box64
box64-rpi4arm64 Box64 built for RPI4ARM64 target. sudo apt install box64-rpi4arm64
box64-rpi3arm64 Box64 built for RPI3ARM64 target. sudo apt install box64-rpi3arm64
box64-tegrax1 Box64 built for Tegra X1 systems. sudo apt install box64-tegrax1
box64-rk3399 Box64 built for rk3399 cpu target. sudo apt install box64-rk3399
box64-android Box64 built with the -DBAD_SIGNAL=ON flag sudo apt install box64-android
box64-rk3588 Box64 built for rk3588 cpu target. sudo apt install box64-rk3588
box64-rpi5arm64 Built for Raspberry Pi 5 (4K page size) sudo apt install box64-rpi5arm64
box64-rpi5arm64ps16k Built for Raspberry Pi 5 (16K page size) sudo apt install box64-rpi5arm64ps16k
box64-lx2160a Built for SolidRun LX2160A Honeycomb (see #24) sudo apt install box64-lx2160a
box64-tegra-t194 sudo apt install box64-tegra-t194
box64-m1 Built for Asahi Linux (M1 macs) sudo apt isntall box64-m1

Want me to build for more platforms? Open an issue.

Note for box86

Please note that this repository is only for box64. If you would like deb packages for box86, check out box86-debs.

badge

box64-debs's People

Contributors

craftyguy avatar ersingencturk avatar hmsjy2017 avatar ryanfortner avatar sevan avatar shenmo7192 avatar theofficialgman avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

box64-debs's Issues

Error running apt update after adding repository to sources.list.d

I am unable to get the Repository Installation instructions to work. After adding the source according to the instructions on this repo:

sudo wget https://ryanfortner.github.io/box64-debs/box64.list -O /etc/apt/sources.list.d/box64.list
wget -qO- https://ryanfortner.github.io/box64-debs/KEY.gpg | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/box64-debs-archive-keyring.gpg 
sudo apt update && sudo apt install box64-rpi4arm64 -y

I get the following error when running apt update:

Get:4 https://box64.debian.ryanfortner.dev/debian ./ InRelease [2115 B]
Err:4 https://box64.debian.ryanfortner.dev/debian ./ InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7759FA1D9FECAC9E
Reading package lists...
GPG error: https://box64.debian.ryanfortner.dev/debian ./ InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7759FA1D9FECAC9E
E: The repository 'https://ryanfortner.github.io/box64-debs/debian ./ InRelease' is not signed.\"

TODO

  • Run builds in parallel (so that if one target fails the whole workflow doesn't break)
  • Switch from checkinstall to a more modern packaging method

version `GLIBC_2.29' not found (required by box64)

This is on Raspberry Pi OS Buster. Am I missing a dependency?

pi@raspberrypi:~ $ sudo apt update && sudo apt install box64 -y
Get:1 https://ryanfortner.github.io/box64-debs/debian ./ InRelease [2,115 B]
Get:2 http://deb.debian.org/debian buster InRelease [122 kB]
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Get:4 http://deb.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:5 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:6 https://ryanfortner.github.io/box64-debs/debian ./ Packages [1,016 B]
Get:7 http://deb.debian.org/debian buster/main armhf Packages [7,698 kB]
Get:8 http://deb.debian.org/debian buster/main arm64 Packages [7,735 kB]
Get:9 http://deb.debian.org/debian buster/main Translation-en [5,968 kB]
Get:10 http://deb.debian.org/debian buster/contrib armhf Packages [40.1 kB]
Get:11 http://deb.debian.org/debian buster/contrib arm64 Packages [38.4 kB]
Get:12 http://deb.debian.org/debian buster/non-free armhf Packages [62.1 kB]
Get:13 http://deb.debian.org/debian buster/non-free arm64 Packages [53.9 kB]
Get:14 http://deb.debian.org/debian buster/non-free Translation-en [88.8 kB]
Fetched 21.9 MB in 12s (1,845 kB/s)                                            
Reading package lists... Done
Building dependency tree       
Reading state information... Done
119 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '10.10' to '10.11'
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  box64
0 upgraded, 1 newly installed, 0 to remove and 119 not upgraded.
Need to get 1,367 kB of archives.
After this operation, 7,709 kB of additional disk space will be used.
Get:1 https://ryanfortner.github.io/box64-debs/debian ./ box64 0.1.5+20211005.348cb572-1 [1,367 kB]
Fetched 1,367 kB in 0s (3,817 kB/s)
Selecting previously unselected package box64.
(Reading database ... 91979 files and directories currently installed.)
Preparing to unpack .../box64_0.1.5+20211005.348cb572-1_arm64.deb ...
Unpacking box64 (0.1.5+20211005.348cb572-1) ...
Setting up box64 (0.1.5+20211005.348cb572-1) ...
Restarting systemd-binfmt...
pi@raspberrypi:~ $ box64
box64: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by box64)

binfmt service, no such file or directory

I installed the box64-arm64 on my acer spin 513, and got an error at the end of apt install, journalctl -xe says:

Aug 22 14:26:47 penguin systemd[1]: Starting Set Up Additional Binary Formats...
░░ Subject: A start job for unit systemd-binfmt.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit systemd-binfmt.service has begun execution.
░░ 
░░ The job identifier is 402.
Aug 22 14:26:47 penguin systemd-binfmt[5336]: Failed to add binary format: No such file or directory
Aug 22 14:26:47 penguin systemd[1]: systemd-binfmt.service: Main process exited, code=exited, status=1/>
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ An ExecStart= process belonging to unit systemd-binfmt.service has exited.
░░ 
░░ The process' exit code is 'exited' and its exit status is 1.

Aug 22 14:26:47 penguin systemd[1]: systemd-binfmt.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ The unit systemd-binfmt.service has entered the 'failed' state with result 'exit-code'.
Aug 22 14:26:47 penguin systemd[1]: Failed to start Set Up Additional Binary Formats.
░░ Subject: A start job for unit systemd-binfmt.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit systemd-binfmt.service has finished with a failure.
░░ 
░░ The job identifier is 402 and the job result is failed.
# /etc/binfmt.d/box64.conf
:x86_64:M::\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x3e\x00:\xff\xff\xff\xff\xff\xff\xff\x00\x00\x00\x00\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/local/bin/box64:
schiffbruechige@penguin:~$ which box64
/usr/local/bin/box64
schiffbruechige@penguin:~$ file `which box64`
/usr/local/bin/box64: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=c0512605f50cd1b5d8ad1d545c0ecd50d345ae4b, with debug_info, not stripped

This all seems vaguely sane, tho I've never done anything with binfmt before.. Any ideas?

Prebuilt image for SolidRun LX2160A Honeycomb?

◢◣ WARNING: There is no box64 pre-build for your device  SolidRun CEX7 Platform Rev 1
◢◣ WARNING: Installing the generic arm box64 build as a fallback (crypto extensions enabled)

I seem to recall at one point checking the features of each build and thinking that the RockChip one is closest, but I don't remember the reasoning.

Note that when booted with U-Boot, the system model is different: SolidRun LX2160A Honeycomb

/proc/cpuinfo:

Architecture:           aarch64
  CPU op-mode(s):       32-bit, 64-bit
  Byte Order:           Little Endian
CPU(s):                 16
  On-line CPU(s) list:  0-15
Vendor ID:              ARM
  BIOS Vendor ID:       NXP
  Model name:           Cortex-A72
    BIOS Model name:    Cortex-A72 0xd08 CPU @ 2.0GHz
    BIOS CPU family:    280
    Model:              3
    Thread(s) per core: 1
    Core(s) per socket: 16
    Socket(s):          1
    Stepping:           r0p3
    BogoMIPS:           50.00
    Flags:              fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid

Output of ArmCpuInfo.efi:

ID_AA64MMFR0_EL1 = 0x0000000000001124
ID_AA64MMFR1_EL1 = 0x0000000000000000
ID_AA64MMFR2_EL1 = 0x0000000000000000
ID_AA64PFR0_EL1  = 0x0000000001002222
ID_AA64PFR1_EL1  = 0x0000000000000000
ID_AA64ISAR0_EL1 = 0x0000000000011120
ID_AA64ISAR1_EL1 = 0x0000000000000000
ID_AA64ISAR2_EL1 = 0x0000000000000000
ID_AA64DFR0_EL1  = 0x0000000010305106

 Register         |  Bits | Value | Feature
------------------|-------|-------|----------------------------------------------
 ID_AA64MMFR0     |  3:0  |  0100 | 44 Bits  (16TB) of physical address range supported.
 ID_AA64MMFR0     |  7:4  |  0010 | ASID: 16 Bits
 ID_AA64MMFR0     | 11:8  |  0001 | Mixed-endian support.
 ID_AA64MMFR0     | 19:16 |  0000 | No mixed-endian support at EL0.
 ID_AA64MMFR0     | 15:12 |  0001 | Supports a distinction between Secure and Non-Secure Memory.
 ID_AA64MMFR0     | 31:28 |  0000 |  4KB granule supported.
 ID_AA64MMFR0     | 43:40 |  0000 | unknown
 ID_AA64MMFR0     | 23:20 |  0000 | 16KB granule not supported.
 ID_AA64MMFR0     | 35:32 |  0000 | unknown
 ID_AA64MMFR0     | 27:24 |  0000 | 64KB granule supported.
 ID_AA64MMFR0     | 39:36 |  0000 | unknown
 ID_AA64MMFR0     | 47:44 |  0000 | FEAT_ExS not implemented.
 ID_AA64MMFR0     | 59:56 |  0000 | FEAT_FGT not implemented.
 ID_AA64MMFR0     | 63:60 |  0000 | FEAT_ECV not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64MMFR1     |  3:0  |  0000 | FEAT_HAFDBS not implemented.
 ID_AA64MMFR1     |  7:4  |  0000 | FEAT_VMID16 not implemented.
 ID_AA64MMFR1     | 11:8  |  0000 | FEAT_VHE not implemented.
 ID_AA64MMFR1     | 15:12 |  0000 | FEAT_HPDS not implemented.
 ID_AA64MMFR1     | 19:16 |  0000 | FEAT_LOR not implemented.
 ID_AA64MMFR1     | 23:20 |  0000 | FEAT_PAN not implemented.
 ID_AA64MMFR1     | 31:28 |  0000 | FEAT_XNX not implemented.
 ID_AA64MMFR1     | 35:32 |  0000 | FEAT_TWED not implemented.
 ID_AA64MMFR1     | 39:36 |  0000 | FEAT_ETS not implemented.
 ID_AA64MMFR1     | 43:40 |  0000 | FEAT_HCX not implemented.
 ID_AA64MMFR1     | 47:44 |  0000 | FEAT_AFP not implemented.
 ID_AA64MMFR1     | 51:48 |  0000 | FEAT_nTLBPA not implemented.
 ID_AA64MMFR1     | 55:52 |  0000 | FEAT_TIDCP1 not implemented
 ID_AA64MMFR1     | 59:56 |  0000 | FEAT_CMOW not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64MMFR2     |  3:0  |  0000 | FEAT_TTCNP not implemented.
 ID_AA64MMFR2     |  7:4  |  0000 | FEAT_UAO not implemented.
 ID_AA64MMFR2     | 11:8  |  0000 | FEAT_LSMAOC not implemented.
 ID_AA64MMFR2     | 15:12 |  0000 | FEAT_IESB not implemented.
 ID_AA64MMFR2     | 19:16 |  0000 | FEAT_LVA not implemented.
 ID_AA64MMFR2     | 23:20 |  0000 | FEAT_CCIDX not implemented.
 ID_AA64MMFR2     | 27:24 |  0000 | FEAT_NV not implemented.
 ID_AA64MMFR2     | 31:28 |  0000 | FEAT_TTST not implemented.
 ID_AA64MMFR2     | 35:32 |  0000 | FEAT_LSE2 not implemented.
 ID_AA64MMFR2     | 39:36 |  0000 | FEAT_IDST not implemented.
 ID_AA64MMFR2     | 43:40 |  0000 | FEAT_S2FWB not implemented.
 ID_AA64MMFR2     | 51:48 |  0000 | FEAT_TTL not implemented.
 ID_AA64MMFR2     | 55:52 |  0000 | FEAT_BBM: Level 0 support for changing block size is supported.
 ID_AA64MMFR2     | 59:56 |  0000 | FEAT_EVT not implemented.
 ID_AA64MMFR2     | 63:60 |  0000 | FEAT_E0PD not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64PFR0      |  3:0  |  0010 | EL0 in AArch64 and AArch32
 ID_AA64PFR0      |  7:4  |  0010 | EL1 in AArch64 and AArch32
 ID_AA64PFR0      | 11:8  |  0010 | EL2 in AArch64 and AArch32
 ID_AA64PFR0      | 15:12 |  0010 | EL3 in AArch64 and AArch32
 ID_AA64PFR0      | 19:16 |  0000 | Floating-point implemented.
 ID_AA64PFR0      | 23:20 |  0000 | Advanced SIMD implemented.
 ID_AA64PFR0      | 27:24 |  0001 | System registers to versions 3.0/4.0 of GIC CPU implemented.
 ID_AA64PFR0      | 31:28 |  0000 | FEAT_RAS not implemented.
 ID_AA64PFR0      | 35:32 |  0000 | FEAT_SVE not implemented.
 ID_AA64PFR0      | 39:36 |  0000 | Secure EL2 not implemented.
 ID_AA64PFR0      | 43:40 |  0000 | FEAT_MPAM not implemented.
 ID_AA64PFR0      | 47:44 |  0000 | FEAT_AMU not implemented.
 ID_AA64PFR0      | 51:48 |  0000 | FEAT_DIT not implemented.
 ID_AA64PFR0      | 55:52 |  0000 | FEAT_RME not implemented
 ID_AA64PFR0      | 59:56 |  0000 | Not disclosed whether FEAT_CSV2 is implemented.
 ID_AA64PFR0      | 63:60 |  0000 | FEAT_CSV3 not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64PFR1      |  3:0  |  0000 | FEAT_BTI not implemented.
 ID_AA64PFR1      |  7:4  |  0000 | FEAT_SSBS not implemented.
 ID_AA64PFR1      | 11:8  |  0000 | FEAT_MTE not implemented.
 ID_AA64PFR1      | 27:24 |  0000 | FEAT_SME not implemented.
 ID_AA64PFR1      | 31:28 |  0000 | FEAT_RNG_TRAP not implemented.
 ID_AA64PFR1      | 39:36 |  0000 | FEAT_NMI not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64ISAR0     |  7:4  |  0010 | FEAT_AES and FEAT_PMULL implemented.
 ID_AA64ISAR0     | 11:8  |  0001 | FEAT_SHA1 implemented.
 ID_AA64ISAR0     | 15:12 |  0001 | FEAT_SHA256 implemented.
 ID_AA64ISAR0     | 19:16 |  0001 | CRC32 instructions implemented.
 ID_AA64ISAR0     | 23:20 |  0000 | FEAT_LSE not implemented.
 ID_AA64ISAR0     | 27:24 |  0000 | TME instructions not implemented.
 ID_AA64ISAR0     | 31:28 |  0000 | FEAT_RDM not implemented.
 ID_AA64ISAR0     | 35:32 |  0000 | FEAT_SHA3 not implemented.
 ID_AA64ISAR0     | 39:36 |  0000 | FEAT_SM3 not implemented.
 ID_AA64ISAR0     | 43:40 |  0000 | FEAT_SM4 not implemented.
 ID_AA64ISAR0     | 47:44 |  0000 | FEAT_DotProd not implemented.
 ID_AA64ISAR0     | 51:48 |  0000 | FEAT_FHM not implemented.
 ID_AA64ISAR0     | 55:52 |  0000 | FEAT_FlagM/FEAT_FlagM2 not implemented.
 ID_AA64ISAR0     | 59:56 |  0000 | FEAT_TLBIOS/FEAT_TLBIRANGE not implemented.
 ID_AA64ISAR0     | 63:60 |  0000 | FEAT_RNG not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64ISAR1     |  3:0  |  0000 | DC CVAP not implemented.
 ID_AA64ISAR1     |  7:4  |  0000 | Address Authentication  (APA) not implemented.
 ID_AA64ISAR1     | 11:8  |  0000 | Address Authentication  (API) not implemented.
 ID_AA64ISAR1     | 15:12 |  0000 | FEAT_JSCVT not implemented.
 ID_AA64ISAR1     | 19:16 |  0000 | FEAT_FCMA not implemented.
 ID_AA64ISAR1     | 23:20 |  0000 | FEAT_LRCPC (2) not implemented.
 ID_AA64ISAR1     | 27:24 |  0000 | FEAT_PACQARMA5 not implemented.
 ID_AA64ISAR1     | 31:28 |  0000 | FEAT_PACIMP not implemented.
 ID_AA64ISAR1     | 35:32 |  0000 | FEAT_FRINTTS not implemented.
 ID_AA64ISAR1     | 39:36 |  0000 | FEAT_SB not implemented.
 ID_AA64ISAR1     | 43:40 |  0000 | FEAT_SPECRES not implemented.
 ID_AA64ISAR1     | 47:44 |  0000 | FEAT_BF16 not implemented.
 ID_AA64ISAR1     | 51:48 |  0000 | FEAT_DGH not implemented.
 ID_AA64ISAR1     | 55:52 |  0000 | FEAT_I8MM not implemented.
 ID_AA64ISAR1     | 59:56 |  0000 | FEAT_XS not implemented.
 ID_AA64ISAR1     | 63:60 |  0000 | FEAT_LS64 not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64ISAR2     |  3:0  |  0000 | FEAT_WFxT not implemented.
 ID_AA64ISAR2     |  7:4  |  0000 | FEAT_RPRES not implemented.
 ID_AA64ISAR2     | 11:8  |  0000 | FEAT_PACQARMA3 not implemented.
 ID_AA64ISAR2     | 15:12 |  0000 | Address Authentication  (APA3) not implemented.
 ID_AA64ISAR2     | 19:16 |  0000 | FEAT_MOPS not implemented.
 ID_AA64ISAR2     | 23:20 |  0000 | FEAT_HBC not implemented.
 ID_AA64ISAR2     | 27:24 |  0000 | FEAT_CONSTPACFIELD not implemented.
------------------|-------|-------|----------------------------------------------
 ID_AA64DFR0      |  3:0  |  0110 | Armv8 debug architecture
 ID_AA64DFR0      |  7:4  |  0000 | Trace unit System registers not implemented.
 ID_AA64DFR0      | 11:8  |  0001 | FEAT_PMUv3 implemented.
 ID_AA64DFR0      | 15:12 |  0101 | Number of breakpoints, minus 1.
 ID_AA64DFR0      | 23:20 |  0011 | Number of watchpoints, minus 1.
 ID_AA64DFR0      | 31:28 |  0001 | Number of breakpoints that are context-aware, minus 1.
 ID_AA64DFR0      | 35:32 |  0000 | FEAT_SPE not implemented.
 ID_AA64DFR0      | 39:36 |  0000 | FEAT_DoubleLock implemented.
 ID_AA64DFR0      | 43:40 |  0000 | FEAT_TRF not implemented.
 ID_AA64DFR0      | 47:44 |  0000 | FEAT_TRBE not implemented.
 ID_AA64DFR0      | 51:48 |  0000 | FEAT_MTPMU not implemented.
 ID_AA64DFR0      | 55:52 |  0000 | FEAT_BRBE not implemented.
 ID_AA64DFR0      | 63:60 |  0000 | Setting MDCR_EL2.HPMN to zero has CONSTRAINED UNPREDICTABLE behavior.

Apt won't install latest rpi4 build

Hi, I'm trying to install the latest build of box64-rpi4arm64 within a Docker container and it appears the latest available is 0.2.5+20231025.12c40a5-1 (as of writing this issue the latest should be 0.2.5+20231205.24f241a-1). I guess the Packages file isn't up to date.

my Dockerfile used the following to install box64

ADD https://ryanfortner.github.io/box64-debs/box64.list /etc/apt/sources.list.d/box64.list
ADD https://ryanfortner.github.io/box64-debs/KEY.gpg /tmp/KEY.gpg
RUN cat /tmp/KEY.gpg | gpg --dearmor > /etc/apt/trusted.gpg.d/box64-debs-archive-keyring.gpg \
 && apt-get update 
 && apt-get install box64-rpi4arm64 -y 

and debugging shows the old package in apt

# apt policy box64-rpi4arm64
box64-rpi4arm64:
  Installed: 0.2.5+20231025.12c40a5-1
  Candidate: 0.2.5+20231025.12c40a5-1
  Version table:
 *** 0.2.5+20231025.12c40a5-1 500
        500 https://ryanfortner.github.io/box64-debs/debian ./ Packages
        100 /var/lib/dpkg/status
     0.2.5+20231024.65fc95b-1 500
        500 https://ryanfortner.github.io/box64-debs/debian ./ Packages
     0.2.5+20231023.b3daf55-1 500
        500 https://ryanfortner.github.io/box64-debs/debian ./ Packages

Thanks for providing these packages.

T.

Termux

Is it possible to add termux debs in here with Termux Docker? (Native)

(But adding apt repo is little different in termux due the paths mostly)

Add builds for Ampeere Altra / ADLINK

I guess these are the most used ARM cores on servers, so perfect for steamCMD.

# cat /proc/cpuinfo 
processor       : 0
BogoMIPS        : 50.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x3
CPU part        : 0xd0c
CPU revision    : 1

(this had been shorened to just the first core)

# gcc -c -Q -mcpu=native --help=target
The following options are target specific:
  -mabi=                                lp64
  -march=                     
  -mbig-endian                          [disabled]
  -mbionic                              [disabled]
  -mbranch-protection=        
  -mcmodel=                             small
  -mcpu=                                neoverse-n1+crc+crypto+ssbs
  -mfix-cortex-a53-835769               [enabled]
  -mfix-cortex-a53-843419               [enabled]
  -mgeneral-regs-only                   [disabled]
  -mglibc                               [enabled]
  -mharden-sls=               
  -mlittle-endian                       [enabled]
  -mlow-precision-div                   [disabled]
  -mlow-precision-recip-sqrt            [disabled]
  -mlow-precision-sqrt                  [disabled]
  -mmusl                                [disabled]
  -momit-leaf-frame-pointer             [enabled]
  -moutline-atomics                     [enabled]
  -moverride=<string>         
  -mpc-relative-literal-loads           [enabled]
  -msign-return-address=                none
  -mstack-protector-guard-offset= 
  -mstack-protector-guard-reg= 
  -mstack-protector-guard=              global
  -mstrict-align                        [disabled]
  -msve-vector-bits=<number>            scalable
  -mtls-dialect=                        desc
  -mtls-size=                           24
  -mtrack-speculation                   [disabled]
  -mtune=                     
  -muclibc                              [disabled]
  -mverbose-cost-dump                   [disabled]

  Known AArch64 ABIs (for use with the -mabi= option):
    ilp32 lp64

  Supported AArch64 return address signing scope (for use with -msign-return-address= option):
    all non-leaf none

  The code model option names for -mcmodel:
    large small tiny

  Valid arguments to -mstack-protector-guard=:
    global sysreg

  The possible SVE vector lengths:
    1024 128 2048 256 512 scalable

  The possible TLS dialects:
    desc trad

Would also be nice to have for Box86 but not sure how to get a gcc dump for that target.

Box64 not available on RPi Debian64bit.

Hi.

I'm normally a slackware user but I've been driven onto Debian by poor graphics. I can't install box64, I'm following the instructions in box64/docs/COMPILE.md. I get files from the first 2 lines. Then it says "Unable to locate package box64." Have the paths changed?

"systemd" problems w/ Termux's proot-distro

Setting up box64 (0.1.9+20220529.c312ca4-1) ...
Restarting systemd-binfmt...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
dpkg: error processing package box64 (--configure):
 installed box64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 box64
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@localhost:~#

Debían 11 bullseye
Can you please help?

Prebuilt box64 and box86 for t194 and t234

Please add prebuilt box64 and box86 for t194 and t234
And I suggest to use gcc-13 and newer or clang-16 and newer(specially for t234, due to gcc-10 and older does not support a78ae flag)

Build for qualcom kryo?

Qualcomm® Kryo™ 468 Octa-core 2.10 GHz

Mine is an acer spin 513 (cp513-1h) which apparently has a qualcomm processor.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.