Skip to content

ci: build the aarch64 core in the aarch64 image - #22

Merged
cscd98 merged 1 commit into
libretro:masterfrom
WizzardSK:fix-aarch64-image
Aug 29, 2026
Merged

ci: build the aarch64 core in the aarch64 image#22
cscd98 merged 1 commit into
libretro:masterfrom
WizzardSK:fix-aarch64-image

Conversation

@WizzardSK

Copy link
Copy Markdown

Fixes libretro/libretro-super#2077: hbmame_libretro.so in the Linux aarch64 nightly is an x86-64 binary.

$ file hbmame_libretro.so   # from buildbot.libretro.com/nightly/linux/aarch64/latest/
hbmame_libretro.so: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), ...

My aarch64 job in #13 mirrored the x64 job a little too closely and kept its image: line, so the job ran the amd64 image on the aarch64 runner and produced an amd64 core. Dropping that one line lets the image from linux-aarch64.yml apply. That image installs gcc-12 and gcc-14 at /usr/bin/gcc-12 etc. and defaults gcc to 12, so OVERRIDE_CC/OVERRIDE_CXX still resolve and the job keeps building with the same compiler as x64.

Sorry for the breakage — #13 was the one aarch64 PR I could not build locally (this machine OOMs on hbmame), and this is exactly the kind of thing that slipped through as a result.

The Linux aarch64 job inherited the x64 job's image override, so it ran the
amd64 image on the aarch64 runner and shipped an x86-64 hbmame_libretro.so in
the aarch64 nightly (libretro/libretro-super#2077). Dropping the override lets
linux-aarch64.yml's own image apply; it provides /usr/bin/gcc-12, so the
OVERRIDE_CC/OVERRIDE_CXX pair keeps working unchanged.
@cscd98
cscd98 merged commit 65b1f40 into libretro:master Aug 29, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aarch64 build of hbmame_libretro.so is actually x86-64?

2 participants