From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: riscv@gentoo.org, "Andreas K. Huettel" <dilfridge@gentoo.org>
Subject: Re: [gentoo-dev] How to structure our RISC-V support -- Summary
Date: Sat, 08 May 2021 14:42:21 +0200 [thread overview]
Message-ID: <7497133.a9HWlOh95j@pinacolada> (raw)
In-Reply-To: <14808987.iMDcRRXYNz@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
So, here's what I took away from the thread. Please shout if you
disagree.
1) Advertised riscv profiles will all be non-multilib and use /usr/
lib64 (or /usr/lib if we ever get around to riscv32). [A]
2) The standard for keywording and stabilization is rv64gc/lp64d.
We keep stages for other variants [B] around if feasible, but on these
important packages may be masked and unavailable [C].
3) We try to internally keep the multilib variant with the two-stage
path going for now, as very low-priority thing. [D]
4) Medium term we discuss with the RISC-V, glibc, gcc people how
multilib could be simplified, and then switch the multilib settings
once this comes to a conclusion.
If there are no protests I'll start planning the path migration for
1). (Maybe making a riscv-specific new profile version is best.)
Cheers,
Andreas
[A] Note that the actual specs use /usr/lib32/...
[B] Other ABI (lp64) or other ISA (riscv32...)
[C] See rust etc.
[D] Low priority means, it pretty much won't build every now and then,
as, e.g., right now [E].
[E] Our monkeypatched glibc-2.32 rv32 support was experimental enough
so it didnt survive the transition to official upstream glibc-2.33
support, so the multilib stages will have to be re-bootstrapped.
> So, I would like to bring two proposals up for discussion.
>
> 1) We stop caring about anything except rv64gc/lp64d.
> People can still bootstrap other stuff with crossdev etc, but the
> Gentoo tree and the riscv keyword reflect that things work with
> above -mabi and -march settings.
>
> 2) We drop the multilib paths and use "normal" lib64, with
> additional "safety symlinks" (/usr)/lib64/lp64d -> .
> This is what SuSE and (I think) Fedora already does. The symlink
> should be there since "lib64" is NOT an official fallback coded into
> gcc/glibc/binutils; the only fallback present is "lib" ...
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
prev parent reply other threads:[~2021-05-08 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 20:01 [gentoo-dev] How to structure our RISC-V support Andreas K. Huettel
2021-05-06 20:16 ` Andreas K. Huettel
2021-05-06 20:16 ` [gentoo-dev] " Palmer Dabbelt
2021-05-06 20:16 ` [gentoo-dev] " Michał Górny
2021-05-06 20:30 ` Andreas K. Huettel
2021-05-06 20:34 ` Palmer Dabbelt
2021-05-07 16:11 ` Andreas K. Huettel
2021-05-07 6:15 ` Yixun Lan
2021-05-07 7:38 ` Michał Górny
2021-05-07 16:08 ` Andreas K. Huettel
2021-05-07 6:24 ` Yixun Lan
2021-05-07 16:05 ` Andreas K. Huettel
2021-05-08 12:42 ` Andreas K. Huettel [this message]
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=7497133.a9HWlOh95j@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=riscv@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