Re: Can CT-NG build a RISC-V picolibc toolchain?

--===============0905884886121890725==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Tommy Murphy via crossgcc <[email protected]> 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.

=2D-=20
=2Dkeith

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmMJLxIACgkQ2yIaaQAA
ABGM1w//W790tyHXWRXboVOcKZpuoH+9qFJlKk1oeeVS4L2walK1QWzIVqXD5S4r
ppa5bo6lNL3ClaCxzfXLViHkjyoLhJ0AlYdbqHPeBMhvk98cxq3wtJOL9gQNHswv
KpuAKYN4MdZQc/3hogjZmIRcaIJbwZwNvo9GdevBBjEoVGmMP4C72pjB2Pno2xnE
rYg/fFd/8BMtJRAAtEW+nNB6mIH7pKIQoviJySlUdJGO3rcqJCbfnBVnXJsSoBvh
HB+rS9utHcKBi7A+nE8eR1o35inhJNcryHyX4mDtvVhtcVLvWgB6+F+4l7AaRkN7
FFa1arOAFWDGmy/8Zg1ejRKQ4nXS/zY9+/Ads6Ah6H7iBFPTlpOkRx0VJEcrDLNm
yPHDAlqPhdrcqO/Bj7eaZRuOpoECEAp1FMUANac8afMCDQXzZ8KOQcJLe0Rx77qK
mqqjIYZwjMLpx6RY7Pz7CDVDP/WKxLEdZerIkFFeRt5Duf21RglTYWLy8RGFx6Pn
mKk+4dOjG1pnM1lLwJlhviUDp5h5rjXfOmhddxwZ46uikLvR7x6HIaF1Fr2ts3gx
l8+mdPYhzyNgA01HfMhgs0l9RWNWjwqcjdXJFeGqWhIg7GWNvs+4i9RJkBHolvwc
ePBdk2mvE5Cft5HCdloh07G+uG32B1brCzBdfwOJcdsbo56c8hg=
=nI6R
-----END PGP SIGNATURE-----
--=-=-=--

--===============0905884886121890725==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
For unsubscribe information see http://sourceware.org/lists.html#faq

--===============0905884886121890725==--