From: "R. Diez" <rdiezmail-gcc@yahoo.de>
To: "kai.ruottu@wippies.com" <kai.ruottu@wippies.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Specifying where Binutils is and what it is called
Date: Mon, 20 Apr 2020 09:52:58 +0000 (UTC) [thread overview]
Message-ID: <2007965762.1537196.1587376378163@mail.yahoo.com> (raw)
In-Reply-To: <2007965762.1537196.1587376378163.ref@mail.yahoo.com>
> Maybe in the distant past of GCC there were some problems
> with this "combined build of GCC and newlib" but someone
> suggesting a separate build somewhere nowadays is really weird.
It's not that weird. Many people are using that method:
1) The OpenWrt build system does.
2) The ArchWiki describes that way too:
https://wiki.archlinux.org/index.php/Cross-compiling_tools_package_guidelines
Look for "stage 1" in that page.
3) crosstool-NG is specifically designed to build cross-compilers, and uses the same method:
https://crosstool-ng.github.io/docs/toolchain-construction/
Look for "core pass 1" in that page.
> [...]
> https://docs.rtems.org/releases/4.5.1-pre3/rtemsdoc/html/started/started00072.html
I would not trust the instructions on that page anymore. It's way too old.
> "To bring in newlib and libgloss, a user could link the newlib and
> libgloss subdirectories of the newlib source tree into the src tree of gcc."
> In :
> https://sourceware.org/newlib/faq.html
I would not trust the Newlib documentation very much. Building Newlib for a Linux system (as opposed to the usual embedded system) was broken for years, and it may still be. I would say the project is short on developers.
I did find some information in GCC's own Wiki:
https://gcc.gnu.org/wiki/Building_Cross_Toolchains_with_gcc
But then it says "Create a tree that consists of all of the files from the GCC and binutils/gdb/newlib source trees (including several simulators in src/sim), with the GCC files overriding the binutils/gdb/newlib files when there's a conflict." Overwriting files like that doesn't exactly inspire confidence.
I have invested many hours of work to get a working, tailor-made cross-compiler for my embedded projects. I would even say "wasted a lot of time". I hope you understand that, before investing yet more work, I would like to see some modern, working example (makefile or script) first on how to build a GCC cross-compiler with Newlib in a single step.
Regards,
rdiez
next parent reply other threads:[~2020-04-20 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2007965762.1537196.1587376378163.ref@mail.yahoo.com>
2020-04-20 9:52 ` R. Diez [this message]
[not found] <238241866.1719021.1587558240444.ref@mail.yahoo.com>
2020-04-22 12:24 ` R. Diez
2020-04-23 8:24 ` Christer Solskogen
[not found] <590749852.1515706.1587371249089.ref@mail.yahoo.com>
2020-04-20 8:27 ` R. Diez
2020-04-20 8:47 ` Jonathan Wakely
[not found] <921250919.1086849.1587309283539.ref@mail.yahoo.com>
2020-04-19 15:14 ` R. Diez
2020-04-19 18:49 ` Jonathan Wakely
2020-04-20 5:25 ` Kai Ruottu
2020-04-20 5:32 ` Kai Ruottu
2020-04-20 18:55 ` Jim Wilson
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=2007965762.1537196.1587376378163@mail.yahoo.com \
--to=rdiezmail-gcc@yahoo.de \
--cc=gcc-help@gcc.gnu.org \
--cc=kai.ruottu@wippies.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).