On Sat, 7 Sept 2024 at 07:39, Michael Tokarev <mjt@tls.msk.ru> wrote:
07.09.2024 02:59, Kenneth Adam Miller wrote:
Hello,
I'm on commit bd80b59 and my host is:
$ git desc bd80b59
v2.4.0-rc3-9-gbd80b5963f
Date: Mon Aug 3 11:44:07 2015 +0100
Wow, that is very old. So the answer, in order of preference, is:
(1) don't try to build such an ancient QEMU version: use
recent QEMU instead.
(2) build on (a container of) whatever the contemporary Linux
distro version of the time would have been: QEMU at that
time built on Linux of that time, so it's the mismatch
between new host (system headers, compiler, etc) and old
QEMU that is causing problems.
(3) if you must try to build ancient QEMU on a modern host,
then you are going to run into a pile of more or less
annoying compilation errors, and you're on your own in
figuring out how to fix them. Some strategies:
- if the issue is in part of QEMU you don't care about
then use a configure --disable-foo option to just
not try to compile that feature/etc. e.g. here if you
don't care about Xen support then disable it.
- look through QEMU's commit log and the mailing lists
for the compile message -- often the fix will have
been made in some later QEMU and you could backport it
- otherwise you'll just have to figure out and address
whatever the incompatibility is.