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: Sat, 27 Aug 2022 14:15:05 -0700 [thread overview]
Message-ID: <877d2t8k2u.fsf@keithp.com> (raw)
In-Reply-To: <LO0P265MB68663CD3DC1A1158741FD609F9749@LO0P265MB6866.GBRP265.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Tommy Murphy <tommy_murphy@hotmail.com> 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.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-08-27 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 19:41 Tommy Murphy
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
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=877d2t8k2u.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).