Date: Sun, 12 Dec 2021 19:52:06 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 260299] https://pkg.freebsd.org/FreeBSD:13:aarch64/latest/ is missing *.pkg Message-ID: <bug-260299-7788-uR7nMXBQk2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260299-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-260299-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260299 --- Comment #9 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Brad Davis from comment #8) https://pkg-status.freebsd.org/?all=3D1 shows the main-armv7 builds are happening on a regular basis (3 to 5 times a month). But they result in: stopped:crashed: or, in some cases, the first port failed (pkg) and everything else was skipped. For the stopped:crashed: ones, 15000+ ports were also skipped before the crash. There is no native armv7 build server, nor is an aarch64 one used that can execute armv7 code as well. Instead the builds are attempted on amd64 systems with qemu --and that is problematical. I once tested bulk -a for targeting armv7 on a 16-core Cortex-A72 system (a HoneyComb). As I remember, it took somewhat under a week the way I did it for how I had that system configured (for example: Optane-in-PCIe-slot as the media). It generally went much better than the official builds. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260299-7788-uR7nMXBQk2>