The example used for the below is from 150arm64-default builds on ampere5 (ampere5 and ampere4 are the less time consuming amperes):
. . . =>> Killing timed out build after 172800 seconds . . . Stop. make: stopped making "build" in /usr/ports/www/chromium build of www/chromium | chromium-150.0.7871.46_1 ended at Thu Jul 9 04:06:22 UTC 2026 build time: 2D:00:09:46 !!! build failure encountered !!! To my knowledge, as things are configured for builds on the ampere* official aarch64 builder machines, www/chromium never finishes building but takes about 2 days to for the build attempt to stop for the ampere* that are allowed to try the builds. 172800 seconds is 48 hours. A part of that time it is usually the only thing building. This seems to be the worst of alternatives for ampere[45]: ) It leads to more time between other port package distributions ) It does not provide the advantage of making aarch64 chromium available ) 4 net-mgmt/icingaweb2-module-idoreports@php8* are also unavailable ) 4 net-mgmt/icingaweb2-module-pdfexport@php8* are also unavailable ) 4 net-mgmt/icingaweb2-module-reporting@php8* are also unavailable ) It uses power to no advantage ) It costs money to no advantage The major alternatives being: ) Leave things as they are ) Use blacklist, ignore, or broken status on/for all ampere* ) Adjust the aarch64 configuration such that the builds can complete (I'll not breakout alternative ways to make adjustments) That last may have the disadvantage of taking even more time between the other port package distributions, depending on what was changed to allow builds to complete. As stands, the following are already blacklisted: www/iridium www/ungoogled-chromium ampere3 and ampere2 only: www/chromium (ampere1 is not in operation) as well as: devel/electron3[789] devel/electron4[01] (That leaves devel/electron42 still building at this point.) ampere4 only: devel/llvm-cheri -- === Mark Millard marklmi at yahoo.com
