From: "Electronic Consult" <electronicconsult1@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: Re: Modify target 'march' for RISCV VisionFive 2
Date: Sun, 08 Oct 2023 14:37:47 -0700 [thread overview]
Message-ID: <16294.1696801067627543753@lists.yoctoproject.org> (raw)
In-Reply-To: <CAGUWaEETBbUr__2eC3_chYxCQHqbwQujKyJp5KBTZZt_X76zTw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
I'm using a KAS setup ( https://github.com/OOHehir/build-riscv/blob/main/poky-qt-visionfive2.yml ) & added the following line:
TUNE_CCARGS = "-march=rv64imafdc_zicsr_zifencei_zihintpause"
It seems to have resulted in a successful build of qtbase (following rebuilds of gcc etc)
I imagine there's a more correct way to achieve this however.
[-- Attachment #2: Type: text/html, Size: 419 bytes --]
next prev parent reply other threads:[~2023-10-08 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 16:44 Modify target 'march' for RISCV VisionFive 2 Electronic Consult
2023-10-06 16:52 ` [yocto] " Khem Raj
2023-10-08 13:15 ` Electronic Consult
2023-10-08 21:37 ` Electronic Consult [this message]
2023-10-09 2:47 ` Khem Raj
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=16294.1696801067627543753@lists.yoctoproject.org \
--to=electronicconsult1@gmail.com \
--cc=yocto@lists.yoctoproject.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