I'm not sure how I was _supposed_ to do this, but I checked out the official release and then switch to the hirsute-delta-as-commits-lp1921664 (6c7e3708580ac50f78261a82b2fcdc2f288d6cea) branch which kept the directories around. I configured with "--target-list=riscv64-softmmu" to save time and the resulting binary did *not* reproduce the bug.
So in summary:
- Debian 1:5.2+dfsg-9ubuntu1 reproduces the issue of both RPi4 and my M1 VM.
- So far no version I have built have reproduced the issue.
Definitely makes either _how_ I built it or the _build tools_ I used sus
I'm not sure what to do next. I assume I'm supposed to set the bug back to "new"?
I'm not sure how I was _supposed_ to do this, but I checked out the official release and then switch to the hirsute- delta-as- commits- lp1921664 (6c7e3708580ac5 0f78261a82b2fcd c2f288d6cea) branch which kept the directories around. I configured with "--target- list=riscv64- softmmu" to save time and the resulting binary did *not* reproduce the bug.
So in summary:
- Debian 1:5.2+dfsg-9ubuntu1 reproduces the issue of both RPi4 and my M1 VM.
- So far no version I have built have reproduced the issue.
Definitely makes either _how_ I built it or the _build tools_ I used sus
I'm not sure what to do next. I assume I'm supposed to set the bug back to "new"?