https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253718
Mark Millard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Mark Millard <[email protected]> --- (In reply to dmilith from comment #3) Step by step instructions to setup the context for the failure and then to do what demonstrates the failure in this poudiere context (13.0-RC3+ or main [14])? How many complications (such as virtual machine involvement) can be avoided and still ge† the problem? At this point, not having any specific context in common with you, I've no good clue on how to test if I can reproduce the problem, including how to avoid involving non-essential things relative to the problem, things that I'm not familiar with. I do port builds via poudriere-devel and I have in the past done cross builds of ports via poudriere (amd64->aarch64 and amd64->armv7). I've not done cross builds of ports in a long time. Cross builds involved qemu executing things and some such were getting hung up a lot back then. I gave up on it. Looking around it seems that some improvements in the area have been made, at least for amd64->aarch64. But I've not tested with the qemu updates. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
