From: Dalas Yoo <dalasyoo@gmail.com>
To: crossgcc@sourceware.org
Subject: GCC cross compiler build failure
Date: Thu, 24 Mar 2022 19:58:27 +0900 [thread overview]
Message-ID: <CALb-SNpXHB5g7TuqvK7ZZ6WBYe1b=m4QA8ouhZm+bBv8C5GeYQ@mail.gmail.com> (raw)
Hi, currently I am working on building the embedded cross compiler from GCC
based on the newlib and the libgloss.
After successfully building and installing the newlib and the libgloss
libraries, I tried the gcc cross compiler and found my cross compiler
toolchain cannot find the crt0.o files in my toolchain
targeting arm-none-eabi.
I searched the build result, and found out that the crt0.o file is built
with some prefixes such as rdimon, nosys, etc. So here's my question.
1. where the "crt0.o" file resides?
2. If the type of the crt0.o files are intended, what specs should be the
default specs for the target arm-none-eabi?
Thank you for your help.
Dalas.
reply other threads:[~2022-03-24 10:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CALb-SNpXHB5g7TuqvK7ZZ6WBYe1b=m4QA8ouhZm+bBv8C5GeYQ@mail.gmail.com' \
--to=dalasyoo@gmail.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).