From: Titus von Boxberg <titus@elbe-informatik.de>
To: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: AW: [crosstool-ng/crosstool-ng] 59a784: No need to copy header; libc_start_file does it.
Date: Sat, 14 Jan 2017 09:00:00 -0000 [thread overview]
Message-ID: <379c44656f8049a1939cb87601b1c448@SOLOWJOW.ELBE.local> (raw)
In-Reply-To: <5879bac34a974_4c8d3fa204635138819f4@hookshot-fe2-cp1-prd.iad.github.net.mail>
Alexey,
could you elaborate on this one?
Why would a sysroot "imply a file system"?
Why would "bare metal" not be an OS? It's simply an OS unknown to the toolchain.
Furthermore, I can't see these relationships you claimed between a sysrooted toolchain and an OS or even target file system.
A sysroot allows (us) to cleanly separate 3rd party libs from compiler/syslibs installation
(which is very favourable if you want to generate a system installation from sysroot but not gratuitous otherwise).
Regards,
Titus
-----Ursprüngliche Nachricht-----
Von: crossgcc-owner@sourceware.org [mailto:crossgcc-owner@sourceware.org] Im Auftrag von Alexey Neyman
Gesendet: Samstag, 14. Januar 2017 06:45
An: crossgcc@sourceware.org
Betreff: [crosstool-ng/crosstool-ng] 59a784: No need to copy header; libc_start_file does it.
Log Message:
-----------
Do not use sysroot in bare metal.
None of the bare metal C library choices (avr-libc, newlib) support installing into sysroot. Nor does it make any sense, since sysroot implies a file system, which in turn implies an OS.
Commit: 949cc86ab755ff4fb5971a304ce97c3885fc360e
https://github.com/crosstool-ng/crosstool-ng/commit/949cc86ab755ff4fb5971a304ce97c3885fc360e
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-13 (Fri, 13 Jan 2017)
Changed paths:
M config/toolchain.in
M scripts/build/cc/100-gcc.sh
M scripts/build/libc/newlib.sh
next prev parent reply other threads:[~2017-01-14 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 5:44 Alexey Neyman
2017-01-14 9:00 ` Titus von Boxberg [this message]
2017-01-16 16:57 ` AW: " Alexey Neyman
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=379c44656f8049a1939cb87601b1c448@SOLOWJOW.ELBE.local \
--to=titus@elbe-informatik.de \
--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).