From: Keith Packard <keithp@keithp.com>
To: Tommy Murphy <tommy_murphy@hotmail.com>,
"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Can CT-NG build a RISC-V picolibc toolchain?
Date: Fri, 26 Aug 2022 13:37:38 -0700 [thread overview]
Message-ID: <87edx291wt.fsf@keithp.com> (raw)
In-Reply-To: <LO6P265MB6876E24141F8B383266F5EC9F9759@LO6P265MB6876.GBRP265.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
Tommy Murphy via crossgcc <crossgcc@sourceware.org> writes:
> Can I use CT-NG to build a RISC-V bare metal toolchain that uses
> picolibc as the standard library? Can I build one that bundles newlib,
> newlib-nano and picolibc which can be switched between using the
> relevant specs files as can be done for Arm?
Yup. The "trick" is that newlib-nano and picolibc are 'companion'
libraries, so you won't find them in the obvious place in the
menus. That was the easy way to integrate all three C libraries into the
existing ct-ng code.
I just tried building a riscv toolchain with ct-ng master and it worked
fine. I started with riscv32-unknown-elf, added multilib, newlib-nano
and picolibc. I did have to explicitly disable default-pie.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-08-26 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 19:41 Tommy Murphy
2022-08-26 19:41 ` Tommy Murphy
2022-08-26 20:37 ` Keith Packard [this message]
2022-08-26 21:09 ` Tommy Murphy
2022-08-26 21:09 ` Tommy Murphy
2022-08-27 14:22 Tommy Murphy
2022-08-27 14:22 ` Tommy Murphy
2022-08-27 20:11 ` Tommy Murphy
2022-08-27 20:11 ` Tommy Murphy
2022-08-27 21:15 ` Keith Packard
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=87edx291wt.fsf@keithp.com \
--to=keithp@keithp.com \
--cc=crossgcc@sourceware.org \
--cc=tommy_murphy@hotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).