Feedback-ID: id4c44089:Fastmail
User-Agent: Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27
Mime-Version: 1.0
Message-Id: <0dbfc407-053d-44d2-bbea-137b89dc46c5@www.fastmail.com>
In-Reply-To: <CKADBYGCT8UC.DXMH0IJ5LUMJ@sumire>
References: 
 <CADH9QNoHup814iMEzuALEOb2RzjoPun0FpJ86Aoyf+254yMHfg@mail.gmail.com>
 <CKABOUO79C9A.2GI24CI6UJ6TJ@sumire>
 <CADH9QNoxnBJH26JNOJrKdigqaubJHDx8W1bfNvvdsbt5v_T5xQ@mail.gmail.com>
 <CKADBYGCT8UC.DXMH0IJ5LUMJ@sumire>
Date: Fri, 27 May 2022 09:23:41 -0500
From: "Winston Weinert" <winston@ml1.net>
To: ~alpine/users@lists.alpinelinux.org
Subject: Re: Can't start neovim
Content-Type: text/plain

This was a problem with openttd as well. Same exact issue. I'm wondering if there's impact beyond these two packages? Any way to audit releases to verify correct cpu features are targeted? It seems like an easy pitfall for packagers. 

-- 
  Winston Weinert
  winston@ml1.net
  https://winny.tech/

On Fri, May 27, 2022, at 02:33, alice wrote:
> On Fri May 27, 2022 at 8:53 AM CEST, Samarul Meu wrote:
>> On Fri, May 27, 2022 at 9:16 AM alice <alice@ayaya.dev> wrote:
>> >
>> > this is probably because the luajit apkbuild has -msse4.2 for x86_64.
>> > there is already an issue for it[0], not sure i remember why it was set
>> > that way (aside from being recommended).
>> This means I will not be able to run nvim on my machine?
> probably, post in the issue and see if perhaps jirutka feels like
> changing it