From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Johannes Krottmayer <johannes@krotti42.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Difference between *-none-elf and *-linux-gnu configurations
Date: Fri, 12 Apr 2024 16:14:18 +0100 [thread overview]
Message-ID: <CAH6eHdQzWkOMdPLfQVEKT+Y1TAVT4sH+D8G0eY5WEHy7QKCAmA@mail.gmail.com> (raw)
In-Reply-To: <ef3506d2-5c13-4356-8b63-202b546b601c@krotti42.com>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
On Fri, 12 Apr 2024, 15:26 Johannes Krottmayer via Gcc-help, <
gcc-help@gcc.gnu.org> wrote:
> Hi!
>
> Sorry if already asked, but what are the differences from as example
> x86_64-none-elf and x86_64-linux-gnu configurations?
>
The former is a bare metal "freestanding" target that generates code for a
system without an OS or C library. The latter is a "hosted" target that
uses the Linux kernel and Glibc C library.
> I have tried to compile Linux with a x86_64-none-elf build, but failed with
> assembler errors. (It's might be also a binutils question.) With the
> x86_64-linux-gnu build, everything worked fine.
>
You need a binutils configured for x86_64-none-elf to assemble and link
code compiled for that target.
> Can somebody explain me the key differences between this both builds?
> Unfortunately I currently didn't find any information.
>
> Thanks in advance!
>
> Kind regards,
>
> Johannes
>
next prev parent reply other threads:[~2024-04-12 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 14:24 Johannes Krottmayer
2024-04-12 15:14 ` Jonathan Wakely [this message]
2024-04-12 16:03 ` Johannes Krottmayer
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=CAH6eHdQzWkOMdPLfQVEKT+Y1TAVT4sH+D8G0eY5WEHy7QKCAmA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=johannes@krotti42.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).