From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Dalas Yoo <dalasyoo@gmail.com>
Cc: newlib@sourceware.org
Subject: Re: cannot find crt0.o file
Date: Fri, 25 Mar 2022 11:58:50 +0100 [thread overview]
Message-ID: <5f850b5d-cbfb-4114-5b76-26628b8130f3@yahoo.de> (raw)
In-Reply-To: <CALb-SNqjk7Ts3hr3jXNDOnqZBfcMQBp1AbbhT_BDRUXe6OGxxA@mail.gmail.com>
> [...]
> With the configuration, the newlib was successfully built. But when trying
> to compile and link the program, the arm-none-eabi-gcc prints error "crt0.o
> not found".
This is a common annoyance with GCC for ARM. I filed a request about it more than 5 years ago:
Bug 68605 - Add -mno-crt0 to disable automatic crt0 injection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68605
I normally just add an empty file called crt0.c (or crt0.cpp) to my project, search for it here:
https://github.com/rdiez/JtagDue/blob/master/Project/Makefile.am
The comments around it should provide you with enough information.
Regards,
rdiez
next prev parent reply other threads:[~2022-03-25 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 10:30 Dalas Yoo
2022-03-25 10:58 ` R. Diez [this message]
2022-03-25 12:10 ` Dalas Yoo
2022-04-08 14:05 ` Richard Earnshaw
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=5f850b5d-cbfb-4114-5b76-26628b8130f3@yahoo.de \
--to=rdiezmail-newlib@yahoo.de \
--cc=dalasyoo@gmail.com \
--cc=newlib@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).