Re: Can CT-NG build a RISC-V picolibc toolchain?
Keith Packard via crossgcc <[email protected]> Sat, 27 Aug 2022 14:15:05 -0700
| Newsgroups | gmane.comp.gcc.cross-compiling |
|---|---|
| Message-ID | <[email protected]> |
--===============6664826487123438137== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Tommy Murphy <[email protected]> writes: > Hi Keith > > So, my (non multilib for now) build of the RISC-V tools with newlib, > newlib-nano and picolibc succeeded. I also had to disable the PIC > option. With it enabled the picolibc build failed with an error about > not being able to find the dynamic linker (sorry, forgot to save the > verbatim error). Do you have the idea why that happens? I guess that > PIC is largely, or maybe totally, irrelevant for a bare metal > toolchain with no shared lib requirements? Yup, you don't need pic as you won't have a dynamic linker. > Thanks again for your help in making progress on this. Glad you got it working. =2D-=20 =2Dkeith --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEw4O3eCVWE9/bQJ2R2yIaaQAAABEFAmMKiVkACgkQ2yIaaQAA ABGNiBAAjtPe7QkQ4RLnVh3mKEw06yrXSdx1Xq2k85QdukdktiSYAgwa8oGg5yp7 YtXF3LKFE8her0ektW5DiBpvWyRzwbCmxSTwUsCOt6JvY9GpSm57ZMNVw9foK467 vNGXW4DefgRMajGXcUOv3i6vwb4CqiOczw1IucQDL3w2iRGMqZS2osYiMV9y+H54 YE0AJO57V8jDHBxYtadi1AQHbsIkNTZS0wciCDLHuv3xhTvFYVT3kwKMRJwrwOCf dlo26o++smRY311ZTSlGbXcu6tD6cKDmtcea6y8k+cAFuqoWn/sIpL9xrJNENHwc vUdhLq/raJ9QkHS4AAGXPwPf1ByzQNdP4lMR+7wK639Jwc5zHm8tnPwbOW/8US0W VMF+xRRPxK/zf+t2KIUn6702sILn+OWNSAQJWUsp2PjwerVfE0QT8c7IUhE+E8Iz JfQJNgktOP3rC7EEjhW1OHp5KV/79HgTi6bUYSk/Gbil42mG9k8fCr8sKwTnGyhO 1SQtY3cd5ozdk/+IFCHoIJaNr16RH2QpT2xBM3/bxIcE+szITCZqA8/P1CEp0Ra9 YDeUt+K39VWNLVpTpDA3EYGEVJZmIwLJVPg5Kgc1N9+4ogpJFPbCiJTuQQEsh5vb vMPqVIbdkhM/iveQn9bC4hIWISdS6aQrszlhml08nDrl+ZU2Yxc= =SKZt -----END PGP SIGNATURE----- --=-=-=-- --===============6664826487123438137== 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 --===============6664826487123438137==--