From: dbischof90 <dbischof90@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Various i686 packages do not run on all i686 processors
Date: Thu, 30 Apr 2020 13:31:54 +0200 [thread overview]
Message-ID: <20200430113154.o5tLkFfvkWl0TonVTAUQbK_Z7Ju-KyQ7TVLZZ8GbY7c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21486@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
New comment by dbischof90 on void-packages repository
https://github.com/void-linux/void-packages/issues/21486#issuecomment-621776549
Comment:
That's true, I should have checked that better. I understand the SSE2 restriction, it's the minimal viable common denominator for most of the current packages on x86 32 bit.
I'm just a bit confused as technically almost none of the i686 CPUs are supported if I get that right? (taking a list for example from https://www.linuxquestions.org/questions/linux-hardware-18/what%27s-the-difference-between-i386-i586-and-i686-198431/ ) After all I'm not trying to run on a Pentium I but on one of the later i686. Maybe that can be made more clearer on the webpage.
Is it not viable to include bespoken compiler flag check and provide the SSE2 version in case a compilation with SSE1 is not possible? As mentioned, I see the SSE2 restriction actually only applying for a relative small number of packages (such as FF) and Void could be really a great candidate for old hardware (before one has to fall back to Gentoo for those sweet older laptops). Many of the packages seem to be compiled without SSE2, I can use quite a lot of the packages that xbps provides.
I however also recognize that the number of users that this applies to is most likely limited.
next prev parent reply other threads:[~2020-04-30 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:26 [ISSUE] " dbischof90
2020-04-30 9:58 ` pullmoll
2020-04-30 9:59 ` pullmoll
2020-04-30 10:06 ` pullmoll
2020-04-30 11:31 ` dbischof90 [this message]
2020-04-30 11:32 ` dbischof90
2020-04-30 12:23 ` pullmoll
2020-04-30 12:25 ` pullmoll
2020-04-30 12:32 ` dbischof90
2020-04-30 12:55 ` [ISSUE] [CLOSED] " pullmoll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200430113154.o5tLkFfvkWl0TonVTAUQbK_Z7Ju-KyQ7TVLZZ8GbY7c@z \
--to=dbischof90@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).