No box64 pre-build for bcm2712 (RPi 5) in PI-Apps: Falls back to generic ARM build [upstream confirmed]

[u2rbo-IK]

Confirmations

• I searched for similar bug reports in https://github.com/Botspot/pi-apps/issues and found none were relevant.
• I tried updating Pi-Apps and the issue is still not fixed. How to update Pi-Apps?
• IMPORTANT: I promise to respond to comments on this issue and write a good bug report https://www.softwaretestinghelp.com/how-to-write-good-bug-report/

What happened?

When trying to install Wine (x64) via PI-Apps on a Raspberry Pi 5 Model B Rev 1.1, I receive a warning that no box64 pre-build is available for bcm2712. Then, it installs the generic ARM (box64) build as a fallback.

Description

I attempted to install box64/Wine using PI-Apps on my Raspberry Pi 5 and encountered the following messages:

• WARNING: There is no box64 pre-build for your device bcm2712 Raspberry Pi 5 Model B Rev 1.1
• WARNING: Installing the generic arm box64 build as a fallback (crypto extensions enabled)

This was confirmed by the box64 maintainer as a PI-Apps issue. See: ptitSeb/box64#3667 (comment)

Attempts to update PI-Apps did not resolve the issue.

What are your system specs (run the following command in your terminal)?

OS: Debian GNU/Linux (trixie)
Device model: Raspberry Pi 5 Model B Rev 1.1

(Recommended) Error log? Terminal output? Debug messages?

Output:


WARNING: There is no box64 pre-build for your device bcm2712 Raspberry Pi 5 Model B Rev 1.1
WARNING: Installing the generic arm box64 build as a fallback (crypto extensions enabled)

[Botspot]

AFAIK, this is intended behavior as the Pi 5 has everything most normal generic ARM systems have. As a result, we don't have to disable any features and the generic build works the best on it.

Pinging @theofficialgman in case I'm wrong on that, but if correct I think we should remove this warning as @u2rbo-IK is not the first person I've seen be concerned/confused by the warning.

[matu6968]

AFAIK, this is intended behavior as the Pi 5 has everything most normal generic ARM systems have. As a result, we don't have to disable any features and the generic build works the best on it.

Pinging @theofficialgman in case I'm wrong on that, but if correct I think we should remove this warning as @u2rbo-IK is not the first person I've seen be concerned/confused by the warning.

A PR already exists in Pi-Apps-Coders/box64-debs#13 just it wasn't merged yet

[u2rbo-IK]

Hopefully this helps notify about the existing RP to merge it because it does put a limit on some applications

[theofficialgman]

I'll look into this later today. I think there was a reason gcc-9 wasn't used but could be mistaken.

I think I was also under the impression also that the tuning flags that the pi5 option needed were only included in like gcc-11 and newer (which isn't available on bionic which is used for a number of reasons).

[matu6968]

I'll look into this later today. I think there was a reason gcc-9 wasn't used but could be mistaken.

I think I was also under the impression also that the tuning flags that the pi5 option needed were only included in like gcc-11 and newer (which isn't available on bionic which is used for a number of reasons).

It is since GCC 9 that the cortex-a76 tune flag is present: https://gcc.gnu.org/gcc-9/changes.html#arm-targets

[theofficialgman]

AFAIK, this is intended behavior as the Pi 5 has everything most normal generic ARM systems have. As a result, we don't have to disable any features and the generic build works the best on it.

correct.

I think we should remove this warning as @u2rbo-IK is not the first person I've seen be concerned/confused by the warning.

should probably just drop it, yeah. we don't actually have any evidence there is a notable performance benefit from the cpu specific tuning. it would be nice if @matu6968 you did some performance comparisons in some software between the two builds.