Re: [main has a fix for] armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023
- Reply: Mark Millard : "Re: [main has a fix for] armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023"
- In reply to: Mark Millard : "Re: [main has a fix for] armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 26 Jul 2024 23:44:13 UTC
On Fri, Jul 26, 2024, 5:37 PM Mark Millard <marklmi@yahoo.com> wrote: > On Jul 26, 2024, at 07:56, Philip Paeps <philip@freebsd.org> wrote: > > > On 2024-07-26 22:46:57 (+0800), Mark Millard wrote: > >> So, it looks like updating the kernel and world on ampere2 and > >> enabling builds of main-armv7-default should no longer have > >> main-armv7-default hang-up during graphviz installation (or > >> analogous contexts). Hopefully, that means that > >> main-armv7-default builds will then complete and be distributed. > > > > I've set the stop-builds flag on the ampere machines. I'll kick off a > cluster build and upgrade them when they finish their current builds (or > get stuck). > > > > Thanks for chasing this down. > > FYI: As stands, only main has the update. The MFC will not happen > for about a week. ampere1 and ampere3 should probably wait to > upate until after the MFC since they do not build main-armv7-* . > > Note: The fix is a world change, not a kernel change. So it is > the jail's world that matters. > > I'm not sure if any existing releng/13.*/ or releng/14.*/ will > get an update for this. stable/13/ and stable/14/ are likely to. > I wonder if a rebuilt system will make it through an armv7 bsd-user poudriere bulk.... Warner === > Mark Millard > marklmi at yahoo.com > > >