On Mon, Mar 25, 2024 at 07:12:24PM +0000, Chris Lamb wrote:
Alberto Bertogli wrote:
If you know of a functional official image that I can use to try to
reproduce the problem, or recently-tested steps I can follow to get
a working qemu install, please let me know.
Alas, I can't actually be helpful here. There are no official images
as far as I know… and somewhat annoyingly I (ie. a Debian Developer)
actually have access to some machines set aside for this purpose. I
call this "annoying" because I naturally can't then give you direct
SSH access transitively — but I can proxy ideas, of course.
I totally understand the access part, that's very reasonable on Debian's
part.
But unfortunately, if I can't even run a local VM to try to reproduce
the problem, it's too limiting for me. Especially considering the kind
of issues libfiu often runs into, which tend to be a bit on the esoteric
side :)
Hm, googling the actual error message a little, I think this might be
a bigger issue... or perhaps more accurately, at least one that has
potentially been also solved elsewhere:
* Same think in lightdm: <https://bugs.debian.org/1067561>
* Some kind of "_FILE_OFFSET_BITS"-related patch for v4l-utils
<https://www.spinics.net/lists/linux-media/msg230147.html>
Thank you for looking at this!
I think they could be similar; in particular the second one.
Maybe there's something like `#define pread pread64` in the
architecture's headers that is triggering these errors?
Does this spark anything worth trying? :-)
Maybe seeing the preprocessor output and the actual (temporary) file
getting the complaints could be useful in figuring out what's going on.
That said, even if we find what the problem is, we may keep finding
other issues in the future. If I'm not able to have a VM for this
platform where I can try to reproduce problems, I'm not sure it's viable
to support the package on it :(
Thanks!
Alberto
