From: Stafford Horne <shorne@gmail.com>
To: Gary Lau <zgliu@foxmail.com>
Cc: linux-openrisc <linux-openrisc@vger.kernel.org>
Subject: Re: [Question]or1k-elf/or1k-linux Windows/Cygwin toolchainavailability?
Date: Mon, 14 Jul 2025 16:03:08 +0100 [thread overview]
Message-ID: <aHUcLABF4dBl7641@antec> (raw)
In-Reply-To: <tencent_AB1F05656F2D0DC53C8ECD792547FB8E8707@qq.com>
On Mon, Jul 14, 2025 at 03:06:15PM +0800, Gary Lau wrote:
> Hi Stafford,
>
>
> I found there is already or1k toolchain for windows in below link:
> https://www.embecosm.com/resources/tool-chain-downloads/
Oh, thats right. I forgot about it.
-Stafford
prev parent reply other threads:[~2025-07-14 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-12 7:11 [Question]or1k-elf/or1k-linux Windows/Cygwin toolchain availability? Gary Lau
2025-07-13 5:59 ` Stafford Horne
2025-07-14 9:40 ` [Question]or1k-elf/or1k-linux Windows/Cygwin toolchainavailability? Gary Lau
[not found] ` <tencent_AB1F05656F2D0DC53C8ECD792547FB8E8707@qq.com>
2025-07-14 15:03 ` Stafford Horne [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=aHUcLABF4dBl7641@antec \
--to=shorne@gmail.com \
--cc=linux-openrisc@vger.kernel.org \
--cc=zgliu@foxmail.com \
/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;
as well as URLs for NNTP newsgroup(s).