public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/releng:master commit in: releases/specs-qemu/riscv/
Date: Sat, 30 Jul 2022 18:36:25 +0000 (UTC)	[thread overview]
Message-ID: <1659206175.a689cfab39bd9b9176afe062e36f0abfe9735436.dilfridge@gentoo> (raw)

commit:     a689cfab39bd9b9176afe062e36f0abfe9735436
Author:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 30 18:35:57 2022 +0000
Commit:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Jul 30 18:36:15 2022 +0000
URL:        https://gitweb.gentoo.org/proj/releng.git/commit/?id=a689cfab

Add riscv64 musl softfloat specs

Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>

 releases/specs-qemu/riscv/stage1-lp64-musl.spec | 14 ++++++++++++++
 releases/specs-qemu/riscv/stage3-lp64-musl.spec | 12 ++++++++++++
 2 files changed, 26 insertions(+)

diff --git a/releases/specs-qemu/riscv/stage1-lp64-musl.spec b/releases/specs-qemu/riscv/stage1-lp64-musl.spec
new file mode 100644
index 00000000..83995fdb
--- /dev/null
+++ b/releases/specs-qemu/riscv/stage1-lp64-musl.spec
@@ -0,0 +1,14 @@
+subarch: rv64_lp64_musl
+target: stage1
+version_stamp: @TIMESTAMP@
+interpreter: /usr/bin/qemu-riscv64
+rel_type: musl
+profile: default/linux/riscv/20.0/rv64gc/lp64/musl
+snapshot: @TIMESTAMP@
+source_subpath: musl/stage3-rv64_lp64_musl-latest
+compression_mode: pixz
+decompressor_search_order: xz bzip2
+update_seed: yes
+update_seed_command: -uDN @world
+portage_confdir: @REPO_DIR@/releases/portage/stages-qemu
+portage_prefix: releng

diff --git a/releases/specs-qemu/riscv/stage3-lp64-musl.spec b/releases/specs-qemu/riscv/stage3-lp64-musl.spec
new file mode 100644
index 00000000..818e3a16
--- /dev/null
+++ b/releases/specs-qemu/riscv/stage3-lp64-musl.spec
@@ -0,0 +1,12 @@
+subarch: rv64_lp64_musl
+target: stage3
+version_stamp: @TIMESTAMP@
+interpreter: /usr/bin/qemu-riscv64
+rel_type: musl
+profile: default/linux/riscv/20.0/rv64gc/lp64/musl
+snapshot: @TIMESTAMP@
+source_subpath: musl/stage1-rv64_lp64_musl-@TIMESTAMP@
+compression_mode: pixz
+decompressor_search_order: xz bzip2
+portage_confdir: @REPO_DIR@/releases/portage/stages-qemu
+portage_prefix: releng


             reply	other threads:[~2022-07-30 18:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 18:36 Andreas K. Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-01 20:38 [gentoo-commits] proj/releng:master commit in: releases/specs-qemu/riscv/ Andreas K. Hüttel
2024-04-05 20:50 Andreas K. Hüttel
2024-02-10 11:13 Andreas K. Hüttel
2023-12-11 17:07 Andreas K. Hüttel
2023-12-11 17:07 Andreas K. Hüttel
2023-12-11 16:42 Andreas K. Hüttel
2023-07-10 20:26 Andreas K. Hüttel
2023-07-08 23:12 Andreas K. Hüttel
2022-02-27 15:50 Andreas K. Hüttel
2022-02-27 15:21 Andreas K. Hüttel
2021-10-31 22:06 Georgy Yakovlev
2021-08-21 21:53 Andreas K. Hüttel
2021-06-29 20:16 Andreas K. Hüttel
2021-06-29 20:16 Andreas K. Hüttel
2021-06-23 16:10 Andreas K. Hüttel
2021-06-11 16:19 Andreas K. Hüttel
2021-06-11 15:37 Andreas K. Hüttel

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=1659206175.a689cfab39bd9b9176afe062e36f0abfe9735436.dilfridge@gentoo \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.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