Unable to execute formulas installed by Homebrew on Ubuntu 25.04

[PatTheMav]

Additional Info

• I am using Windows Subsystem for Linux

Output of brew config

HOMEBREW_VERSION: 5.0.12
ORIGIN: https://github.com/Homebrew/brew
HEAD: d01011cac6d72032c75fd2cd9489909e95d9faf2
Last commit: 3 days ago
Branch: stable
Core tap JSON: 28 Jan 16:07 UTC
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_BAT_THEME: mariana
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :0
HOMEBREW_DOWNLOAD_CONCURRENCY: 4
HOMEBREW_EDITOR: /usr/bin/vim
HOMEBREW_FORBID_PACKAGES_FROM_PATHS: set
HOMEBREW_MAKE_JOBS: 2
Homebrew Ruby: 3.4.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/3.4.8/bin/ruby
CPU: dual-core 64-bit arm
Clang: 20.1.2
Git: 2.48.1 => /bin/git
Curl: 8.12.1 => /bin/curl
Kernel: Linux 6.14.0-33-generic aarch64 GNU/Linux
OS: Ubuntu 25.04 (plucky)
Host glibc: 2.41
Host libstdc++: 6.0.34
/usr/bin/gcc-12: 12.4.0
/usr/bin/ruby: N/A
glibc: N/A
gcc@12: N/A
gcc: N/A
xorg: N/A

Output of brew doctor

Your system is ready to brew.

Description of issue

When Linuxbrew was still just Tier 2 on ARM64 machines I was able to use Homebrew just fine with many formulas (that was back with Homebrew 4.x). I recently revisited by setup in the same Ubuntu ARM64 VM and while Homebrew itself seems to work just fine, any binary installed by a formula is unable to execute.

Instead I get the following message for any binary (I've chosen to test with bat):

accessing a corrupted shared library: bat

Running file at least suggests that the correct architecture is used:

/home/linuxbrew/.linuxbrew/Cellar/bat/0.26.1/bin/bat: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /home/linuxbrew/.linuxbrew/lib/ld.so, for GNU/Linux 3.7.0, BuildID[sha1]=e803b29a1e033825987822502f9c2a78bde99085, stripped

So far this seems to affect any bottled formula. Are the ARM64 binaries produced by GitHub Actions incompatible with my ARM64 VM? Is this an expected outcome?

I've already tried removing Linuxbrew entirely and starting from scratch with a "clean" environment, but ended up in the same situation.

[PatTheMav]

So I did some debugging locally and it turns out that for some reason Homebrew creates (and indeed re-creates) the following symlink:

lrwxrwxrwx 1 vmuser vmuser 27 Feb  2 14:31 /home/linuxbrew/.linuxbrew/lib/ld.so -> /lib64/ld-linux-x86-64.so.2

If I remove this symlink and replace it with a link to /lib/ld-linux-aarch64.so.1, all installed Homebrew packages execute just fine.

However this symlink is "broken" automatically whenever a new Homebrew formula is installed. I'd expect there to be a larger volume of GitHub issues if this were indeed a wide-spread issue, so I now wonder if there is some local state or environment hint that makes Homebrew pick up the linker library for the wrong architecture..

[PatTheMav]

I guess this will do it:

https://github.com/Homebrew/brew/blob/90ed3077706519befc37fd2832334b9cad23e80c/Library/Homebrew/os/linux/ld.rb#L11-L20

As read that as "as long as /lib64/ld-linux-x86-64.so.2 is present on the system, it will take higher precedence as the native architecture's /lib/ld-linux-aarch64.so.1.