Re: A better alternative to having builds of main-armv7-default fully disabled and last-built be months out of date

From: Michal Meloun <meloun.michal_at_gmail.com>
Date: Sun, 07 Jul 2024 04:35:06 UTC

On 07.07.2024 5:42, Mark Millard wrote:
> main's armv7 packages that are distributed are getting to be months
> behind because of the build hangups preventing the builds on ampere2.
> 
> The hangups happen just-after graphics/graphviz installation during
> the activity in a builder where that build depends on
> graphics/graphviz .
> 
> I expect that the armv7 "bulk -a" builds on ampere2 would complete
> if the Makefile for graphics/graphviz had:
> 
> BROKEN_armv7=	leads to ampere2 build hangups for builds that depended on graphics/graphviz
> 
> A related subset of the packages would not be built at all. But that
> is better for security and such than the official packages that are
> available being systematically months out of date, at least in my view.
> 
> I suggest trying the chnage and enabling main-armv7-default builds
> to see if they complete overall.
> 
> I'll note that there is a  hostorical example of a graphics/giflib
> build failure that lead to 3481 ports not being built, including
> graphics/graphviz . But the "bulk -a" completed and 24176 packages
> built and were distributed.
> 
> graphics/graphviz having BROKEN_armv7 should generaelly build more
> packages than that when graphics/giflib builds okay.
> 
> ===
> Mark Millard
> marklmi at yahoo.com
> 
> 
graphics/graphviz can be built on native armv7 without any problems, so 
it looks like a compat32 problem. Unfortunately I don't have my 
honeycomb ready to test this inside arm32 jail.

Are you able to try to prepare some testcase? I've seen some strange 
live lockups in arm32 jail, but never managed to reproduce it.

Michal