From: cp0613@linux.alibaba.com
To: openembedded-core@lists.openembedded.org
Cc: Chen Pei <cp0613@linux.alibaba.com>
Subject: [meta-oe] [PATCH V2 1/2] Support bitbake compilation when the host is a RISCV platform
Date: Tue, 15 Nov 2022 20:03:15 +0800 [thread overview]
Message-ID: <20221115120314.325-1-cp0613@linux.alibaba.com> (raw)
In-Reply-To: <6D11494A-84C4-446D-A736-49841179EC70@arm.com>
From: Chen Pei <cp0613@linux.alibaba.com>
I have a RISCV board running Ubuntu, and then clone the bitbake, meta-oe... to compile,
just like using yocto in ARM board, so I need to add machine-sdk:riscv64 to support it.
Signed-off-by: Chen Pei <cp0613@linux.alibaba.com>
---
meta/conf/machine-sdk/riscv64.conf | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta/conf/machine-sdk/riscv64.conf
diff --git a/meta/conf/machine-sdk/riscv64.conf b/meta/conf/machine-sdk/riscv64.conf
new file mode 100644
index 0000000000..155c195d7d
--- /dev/null
+++ b/meta/conf/machine-sdk/riscv64.conf
@@ -0,0 +1,3 @@
+SDK_ARCH = "riscv64"
+ABIEXTENSION:class-nativesdk = ""
+
--
2.25.1
next prev parent reply other threads:[~2022-11-15 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 9:12 [meta-oe] [PATCH 1/2] Support for building on RISCV cp0613
2022-11-12 9:12 ` [meta-oe] [PATCH 2/2] " cp0613
2022-11-12 18:47 ` [OE-core] " Khem Raj
2022-11-15 11:20 ` [OE-core] [meta-oe] [PATCH 1/2] " Ross Burton
2022-11-15 12:03 ` cp0613 [this message]
2022-11-15 12:11 ` [OE-core] [meta-oe] [PATCH V2 1/2] Support bitbake compilation when the host is a RISCV platform Alexander Kanavin
2022-11-15 12:15 ` cp0613
2022-11-15 12:03 ` [meta-oe] [PATCH V2 2/2] " cp0613
2022-11-15 12:13 ` [OE-core] " Alexander Kanavin
2022-11-15 12:17 ` cp0613
2022-11-15 12:10 ` [meta-oe] [PATCH 1/2] Support for building on RISCV cp0613
2022-11-15 12:24 ` [meta-oe] [PATCH V3 1/2] machine-sdk: add a risv64 definition cp0613
2022-11-15 12:24 ` [meta-oe] [PATCH V3 2/2] meson: set dynamic-linker for riscv64 targets cp0613
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=20221115120314.325-1-cp0613@linux.alibaba.com \
--to=cp0613@linux.alibaba.com \
--cc=openembedded-core@lists.openembedded.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