Re: 4-core arm armv7-package-building configuration notes, on RPi4B (aarch64) and OrangePi+2ed (armv7), poudriere-devel based

[Fixing some over general wording: I missed a qualifier.]

On Mar 15, 2024, at 09:33, Mark Millard <marklmi@yahoo.com> wrote:

> On Mar 15, 2024, at 01:59, Oliver Epper <oliver.epper@gmail.com> wrote:
> 
>> I can only suggest deploying a Mac Mini M1 with qemu using Apple HVF as a poudriere server for aarch64.
>> See https://oliver-epper.de/posts/poudriere-on-m1-mac/
>> 
>> I never had success with qemu emulation on amd64 and the Mac Mini builds rust and llvm without problems. I don't think I'd like to wait for these packages to build on a pi.
> 
> My notes are about building armv7 (32-bit) ports into packages,
> not aarch64 ports into packages (not 64-bit).
> 
> All Apple's arm implementations

All Apple's M* arm implementations . . .

> do not support armv7 code as I
> understand. qemu based emulation would be required in order to
> build armv7 packages form ports in that context.
> 
> But things would largely be the same for building aarch64 ports
> into packages. RPi5/RPi4B's or analogous small arm boards from
> others may be more common overall. (I just happen to have access
> to RPi*'s instead of other alternative small arm boards. So I
> used what I've got.)
> 
> My notes are intended to be suggestive about effective
> poudriere-devel based pacakge building use for folks using such
> small arm boards, at least those with 4 cores and 2 GiBytes+
> RAM. On systems with more cores or 32 GiBytes of RAM, I do
> various things differently.

===
Mark Millard
marklmi at yahoo.com