From: pullmoll <pullmoll@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 12:06:29 +0200 [thread overview]
Message-ID: <20200430100629.8V3xninMJfLVXP7kXT0zAvQo-aj8eK1YWkwMkY6ZB04@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: 932 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/21486#issuecomment-621735103
Comment:
See [minimum requirements](https://docs.voidlinux.org/installation/base-requirements.html) for Void Linux CPU architectures.
If you wanted to have Void for `i[345]86` you'd have to fork `void-packages`, create new entries for e.g. `common/cross-profiles/i586.sh`, create a new `cross-i586-linux-gnu` cross compiler package and then try to cross build a `base-chroot` for `i586`with that. If you get this working, you could then try to (cross) build packages you need.
Note, however, that some packages in `void-packages` are not prepared to build w/o SSE2 support. You'd have to modify them to detect the `i586` vs. `i686` case.
I'm sure I'm missing quite a few places where additional changes would be required. All in all I wouldn't try to do this but rather get at least a P4.
next prev parent reply other threads:[~2020-04-30 10:06 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 [this message]
2020-04-30 11:31 ` dbischof90
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=20200430100629.8V3xninMJfLVXP7kXT0zAvQo-aj8eK1YWkwMkY6ZB04@z \
--to=pullmoll@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).