From: Josef Wolf <jw@raven.inka.de>
To: gcc-help@gcc.gnu.org
Subject: Re: How to properly link libgcc in -ffreestanding mode?
Date: Wed, 27 Jan 2021 13:43:52 +0100 [thread overview]
Message-ID: <20210127124351.GB29238@raven.inka.de> (raw)
In-Reply-To: <alpine.LNX.2.20.13.2101271504560.2464@monopod.intra.ispras.ru>
On Wed, Jan 27, 2021 at 03:07:45PM +0300, Alexander Monakov wrote:
> On Wed, 27 Jan 2021, Josef Wolf wrote:
> [...]
> > What am I missinghere? Any help?
>
> On the command line, libraries need to come after object files that need them,
Umm! I knew that but managed to forget it :-/
Thanks a lot! Woks now.
--
Josef Wolf
jw@raven.inka.de
prev parent reply other threads:[~2021-01-27 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 11:54 Josef Wolf
2021-01-27 12:07 ` Alexander Monakov
2021-01-27 12:42 ` Jonathan Wakely
2021-01-27 12:43 ` Josef Wolf [this message]
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=20210127124351.GB29238@raven.inka.de \
--to=jw@raven.inka.de \
--cc=gcc-help@gcc.gnu.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).