public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Tommy Murphy <tommy_murphy@hotmail.com>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Can CT-NG build a RISC-V picolibc toolchain?
Date: Fri, 26 Aug 2022 19:41:05 +0000	[thread overview]
Message-ID: <LO6P265MB6876E24141F8B383266F5EC9F9759@LO6P265MB6876.GBRP265.PROD.OUTLOOK.COM> (raw)
Message-ID: <20220826194105.71RS5_YgfXCmGWNsftwitjAsLcoN9IxmjX7jI_L0oTM@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

Hi there

Apologies in advance if this is a dumb question or one that has been answered already but I tried searching but couldn't find anything on it...

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?

If so, what configuration settings do I need? I can't see a way to do this using the menuconfig. If it's possible, does it perhaps need a manually edited config file?

I've been playing with the latest CT-NG cloned from the master branch in github. I've enabled the experimental option in order to be able to build a RISC-V newlib toolchain which works fine. But I can't see a way to build a picolibc one or a newlib/newlib-nano/picolibc one. I've also used one of the sample configurations to build an Arm multilib toolchain that bundles newlib/newlib-nano/picolibc.

Thanks a lot for any guidance/advice.

             reply	other threads:[~2022-08-26 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26 19:41 Tommy Murphy [this message]
2022-08-26 19:41 ` Tommy Murphy
2022-08-26 20:37 ` Keith Packard
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=LO6P265MB6876E24141F8B383266F5EC9F9759@LO6P265MB6876.GBRP265.PROD.OUTLOOK.COM \
    --to=tommy_murphy@hotmail.com \
    --cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).