Date: Tue, 29 Jul 2025 01:02:25 +0100
From: Naomi Rennie-Waldock <naomi.renniewaldock@gmail.com>
To: ~alpine/users@lists.alpinelinux.org
Subject: Re: Illegal instruction on running vaultwarden on RPI (aarch64)
User-Agent: Thunderbird for Android
In-Reply-To: <802f131142861be76b960bcac52d9e5a@friedersdorff.com>
References: <20250725094929.2abbb421@baryte> <20250725113320.6b69e6f9@bonsai.doitto.me.uk> <20250725120957.6e0e293a@baryte> <01D48CB4-56E1-4229-8569-88494A66814E@gmail.com> <802f131142861be76b960bcac52d9e5a@friedersdorff.com>
Message-ID: <54D042BA-0839-4DF3-8BF7-91000E0BF05B@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 27 July 2025 12:59:21 BST, max@friedersdorff=2Ecom wrote:
>> Are you able to try rebuilding the mimalloc2 with -DMI_NO_OPT_ARCH=3DON=
 added to the cmake arguments?
>
>I have successfully built mimalloc2 with that option=2E  I also had to di=
sable checks, but I think only because the timeout set in the checks was to=
o aggressive for the anemic Raspberry Pi 4=2E
>
>This has solved this issue at though, my password manager is back up!
>
>Thanks for you help!
>
>Question then, does that represent a bug in the APKBUILD for the mimalloc=
2 package? Should I raise a Merge Request to add this compile time option?
>
>Thanks all
>Max

Good to hear!

The optimizations should definitely be disabled in the aport, a lot of our=
 supported ARM devices don't support those instructions=2E