From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:catalyst-3.0-stable commit in: catalyst/arch/
Date: Wed, 23 Dec 2020 15:01:42 +0000 (UTC) [thread overview]
Message-ID: <1608735688.a11c83396d0d4a83644de3e8e6f3f9bd02d5563c.dilfridge@gentoo> (raw)
commit: a11c83396d0d4a83644de3e8e6f3f9bd02d5563c
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Wed Dec 23 14:58:36 2020 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Wed Dec 23 15:01:28 2020 +0000
URL: https://gitweb.gentoo.org/proj/catalyst.git/commit/?id=a11c8339
Fix builder entries for riscv32
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
catalyst/arch/riscv.py | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/catalyst/arch/riscv.py b/catalyst/arch/riscv.py
index 18695b51..1fb2c69b 100644
--- a/catalyst/arch/riscv.py
+++ b/catalyst/arch/riscv.py
@@ -29,14 +29,16 @@ class arch_rv64_lp64(generic_riscv):
generic_riscv.__init__(self,myspec)
class arch_rv32_ilp32d(generic_riscv):
- "builder class for rv64_lp64"
+ "builder class for rv32_ilp32d"
def __init__(self,myspec):
generic_riscv.__init__(self,myspec)
+ self.settings["CHOST"]="riscv32-unknown-linux-gnu"
class arch_rv32_ilp32(generic_riscv):
- "builder class for rv64_lp64"
+ "builder class for rv32_ilp32"
def __init__(self,myspec):
generic_riscv.__init__(self,myspec)
+ self.settings["CHOST"]="riscv32-unknown-linux-gnu"
def register():
next reply other threads:[~2020-12-23 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 15:01 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-11 12:53 [gentoo-commits] proj/catalyst:catalyst-3.0-stable commit in: catalyst/arch/ Andreas K. Hüttel
2022-08-13 11:35 Andreas K. Hüttel
2022-07-30 18:41 Andreas K. Hüttel
2022-04-23 13:24 Andreas K. Hüttel
2022-02-27 15:46 Andreas K. Hüttel
2020-09-17 21:03 Andreas K. Hüttel
2020-07-18 17:19 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=1608735688.a11c83396d0d4a83644de3e8e6f3f9bd02d5563c.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