Hi Étienne,
Thank you very much for your reply. Luckily I found out the same route
(using qemu) myself and fixed the problem All architectures are now
green in tracker: https://buildd.debian.org/status/package.php?p=mrc
regards, -maarten
Op 12-09-2021 om 15:59 schreef Étienne Mollier:
Hi Maarten,
Maarten L. Hekkelman, on 2021-09-02:
I found the underlying problem, apparently the ABI field of the ELF header
should contain a flag indicating it is a Linux executable. In order to set
this flag properly, I need to find out various things and perhaps it is
easiest to try to figure out these myself. Is it possible to get access to a
HPPA machine running Debian? I am a Debian maintainer, if that makes any
difference.
Without easy access to a PA-RISC machine, you can resort to
Qemu. The Debian hppa port can be emulated using one of the
emulators provided in the package qemu-system-misc. If you
combine it with the package qemu-user-static (and also have
Debian ports keyring at hand), then you can directly debootstrap
a chroot able to run PA-RISC binaries:
$ uname -m
x86_64
$ sudo debootstrap \
--arch=hppa \
--keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \
--include=debian-ports-archive-keyring \
sid sid-hppa-chroot http://ftp.ports.debian.org/debian-ports
I: Target architecture can be executed
[...]
I: Base system installed successfully.
$ sudo chroot sid-hppa-chroot uname -m
parisc
Otherwise, could you provide me the output of `cpp -dM /dev/null` and
perhaps also how to detect PA-RISC/Debian in a cmake file. That last
question is perhaps a bit too much to ask for, but any hint is appreciated.
Feel free to checkout cpp_hppa.h in attachment; I obtained it
with the aforementioned method.
In hope this helps,
Have a nice day, :)
--
Maarten L. Hekkelman
http://www.hekkelman.com/
