Talk:Embedded Handbook/General/Creating a cross-compiler

Note
Before creating a discussion or leaving a comment, please read about using talk pages. In particular, sign comments using ~~~~ and add new discussions at the bottom of the page. New discussions should be made visible with {{Talk|date = 2024-05-20}}.

== Discussion title ==

{{Talk|date = 2024-05-13}}

A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 11:29, 14 May 2024 (UTC)
:: Another reply [[User:Larry|Larry]] 14:45, 20 May 2024 (UTC)
:: Your reply ~~~~

---

Redlink (Cross-compiler internals)

Talk status

This discussion is done as of 2024-05-08.

Matthew Marchese (maffblaster) , where should the following links point?

Tip
This section is included for posterity and in the hopes that others will find it useful. The target audience is all users who (due to curiosity, naïveté, general misconceptions, and/or their current inability to comprehend this warning) really really want to create their own cross compiler with binutils/(glibc/musl/some other libc)/gcc all by themselves. This section is a synopsys, and lacks the relevant documentation that would prevent the myriad of build failures that may be encountered. If such help is required, see the Beyond section in the handbook for some pointers. Please do not ask for any support at all for this.

Warning
If still reading, it is a very good idea to check out the crosstool project (again refer to the Beyond section) as that provides a distribution independent method for generating cross-compilers. While imperfect, it is certainly the best (and really only) option out there for creating cross-compilers.

— Waldo Lemmer 13:16, 8 May 2024 (UTC)

Unfortunately, I have no idea. That part of the Embedded Handbook didn't exist at the time I ported it to the wiki. These links can be adjusted or removed as far as I'm concerned. Thanks! --Maffblaster (talk) 19:33, 8 May 2024 (UTC)