If there was a port-level view of how the buildbots are doing (maybe there is and I haven't found it?) that might come close.
But from what little I figured out looking at the buildbot pages, it looks like something is failing in an early dependency for arm64. I do not have any arm64 (Apple Silicon) Macs; but I did just set up a Big Sur (x86_64) VM, for familiarity's sake; I'm not ready to move any bare metal over yet. So far, I don't like the look much, but what little I installed (gettext, vim, openmotif, along with whatever they depend on) was painless enough. At least minimally, the macosforge Xquartz seems to work, so likely the MacPorts xorg-server does too. > On Dec 4, 2020, at 21:57, Ryan Schmidt <ryandes...@macports.org> wrote: > > On Dec 4, 2020, at 16:00, James Secan wrote: > >> I think a large number of us are very interested in the status of ports >> vis-a-vis both Apple Silicon (M1) and Big Sur. Some sort of simple >> red-yellow-green status board for ports that have been checked would be very >> useful. > > Unfortunately that information is not reliably available for now. > >> Verified support for the MacPorts codes I use regularly is a major check-box >> on my buy-now list for a new M1 machine. I suspect this is more easily >> visualized than actually produced and maintained. > > Feel free to give us a list of the ports that are important to you and we can > try to find out and/or schedule builds of those ports on our Apple Silicon > build machine and see what happens. > >
