It's not something I've really played around with (running ARM 32 on 64), but I'd start with looking at the dynamic linking for your 32-bit binary with ldd. For example, and just using bash to get some output, you would use the binary that you're trying to get working.
Check what libraries it's trying to pull in and whether it's trying armhf or aarch64 variants for each. I'd probably also ask Behringer support (or any community forums for them) if they had any advice about running their app on a 64 bit machine, as it's probably something that they have encountered before.
Random guess: you might need something in /etc/ld.so.conf.d, maybe, to help the dynamic linker find the armhf libraries. Alternatively, something like using "env LD_LIBRARY_PATH=/lib/something:… ./armhf-binary" to execute it, to adjust the linker paths for just that instance (rather than globally).
Also, https://wiki.debian.org/Multiarch, in case you've not found it. Not sure how helpful it is, or if it's up to date.
Code:
murph@raspberrypi:~ $ ldd /usr/bin/bash linux-vdso.so.1 (0x0000007fbe9ec000) libtinfo.so.6 => /lib/aarch64-linux-gnu/libtinfo.so.6 (0x0000007fbe7e0000) libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000007fbe630000) /lib/ld-linux-aarch64.so.1 (0x0000007fbe9af000)murph@raspberrypi:~ $ Random guess: you might need something in /etc/ld.so.conf.d, maybe, to help the dynamic linker find the armhf libraries. Alternatively, something like using "env LD_LIBRARY_PATH=/lib/something:… ./armhf-binary" to execute it, to adjust the linker paths for just that instance (rather than globally).
Also, https://wiki.debian.org/Multiarch, in case you've not found it. Not sure how helpful it is, or if it's up to date.
Statistics: Posted by Murph9000 — Wed Sep 04, 2024 2:04 am