From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: "pr@gentoo.org" <pr@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] news item: riscv multilib profile is going away
Date: Fri, 04 Sep 2020 12:35:42 +0300 [thread overview]
Message-ID: <6536090.9J7NaK4W3v@farino> (raw)
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
[** Note 1: This only affects one specific profile. **]
[** Note 2: I am still testing the migration process proposed here. **]
Title: riscv multilib profile is going away
Author: Andreas K. Hüttel <dilfridge@gentoo.org>
Posted: 2020-09-06
Revision: 1
News-Item-Format: 2.0
Display-If-Profile: default/linux/riscv/17.0/rv64gc
The Gentoo RISC-V team is discontinuing the riscv64 multilib stages and
profile. The main reason for this is that with the upcoming introduction
of riscv32 a multilib stage would contain both 32bit and 64bit binaries,
and so far no hardware exists that is able to run both and thus update
the stage or installation (unless you use qemu).
Please switch to the rv64gc/lp64d profile. This is done by
* selecting default/linux/riscv/17.0/rv64gc/lp64d with eselect profile
* rebuilding gcc
emerge -1 sys-devel/gcc
* and then rebuilding your system
emerge -ev @world
The default/linux/riscv/17.0/rv64gc profile will stop functioning soon.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, qa, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
reply other threads:[~2020-09-04 9:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6536090.9J7NaK4W3v@farino \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.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