This is the mail archive of the
mailing list for the GCC project.
Re: Exhaustive Instructions for Toolchain Generation
- From: R0b0t1 <r030t1 at gmail dot com>
- To: sandra at codesourcery dot com
- Cc: GCC Development <gcc at gcc dot gnu dot org>
- Date: Tue, 3 Oct 2017 16:27:36 -0500
- Subject: Re: Exhaustive Instructions for Toolchain Generation
- Authentication-results: sourceware.org; auth=none
- References: <CAAD4mYhF0JAkvLcBzHCocB9L5iTd5XU9K33WHeDsJo=_GxqfLg@mail.gmail.com> <CAH6eHdSLuB=uZ4Hseb-CQeT9=E8JTb8=J3yHxBu2DLm7kq=2DA@mail.gmail.com> <CAAD4mYinDcV_Avb9_KwLEmofAiSri_2kHiQrfdu1=LZL0+L3YA@mail.gmail.com> <CAH6eHdTC3yKYy56fZPS4BdCS4y3V2FFHJqhWmgu5VJzj9j-oAA@mail.gmail.com> <CAAD4mYjVnGZkCeezfLEos4QRyYcHJTmgA-322aMRzKVzwFttJA@mail.gmail.com>
On Sun, Oct 1, 2017 at 4:35 PM, Sandra Loosemore <email@example.com>
> On 09/26/2017 03:05 PM, R0b0t1 wrote:
>> I am having problems understanding the build instructions for GCC. I
>> can almost always produce toolchains which function but I can find
>> programs or scripts which do more or less the same thing that produce
>> nonfunctional toolchains or which abort at some stage of compilation.
>> (To clarify: I have no problem compiling the project, but I need help
>> knowing all options which must be configured.)
>> This is related to my questions about generating an arm-none-eabi
>> toolchain, however I also wish to build targets for
>> x86_64-pc-linux-gnu, aarch64-unknown-linux-gnu,
>> powerpc64le-unknown-linux-gnu, etc.
>> Broadly, I have the following questions:
>> 1) What is the complete list of dependencies for a GCC based
>> toolchain? I am led to believe it is: zlib, gmp, mpfr, mpc, isl,
>> expat, binutils, gcc, glibc, and gdb.
>> 2) How do I specify each of the above to be reliant on the versions of
>> other programs that it may depend on being used for the toolchain?
>> Ideally these toolchains would not use system libraries if CHOST is
>> the same as BHOST.
>> 3) Are there any architecture specific options for any of the possible
>> Is there anything else I should be aware of?
> Yes, there are companies (like, ahem, the one I work for --
> CodeSourcery/Mentor/Siemens) who provide contract services for complete
> custom toolchains. Generally speaking, many of our customers find that
> building a complete set of tools requires a lot of obscure knowledge and
> too error-prone to do by hand, whereas we've developed a lot of scripting
> and automated build/test infrastructure to leverage on. So it's more
> cost-effective to hire us to do the work than to thrash around trying to
> If you can provide some more details about what your goals are, I can pass
> that along to our business/sales people to follow up on.
I decline to do your company's market research for them. They could choose
to pay me, of course. Based on the failures I am experiencing I doubt that
your company has gotten the build process entirely correct. Eventually the
details of my research will be released, as I enjoy
___ _____ _ _ __ __
|_ || _ | | | | \ \ / /
| || | | | | | | \ V /
| || | | | | | | \ /
/\__/ /\ \_/ / |____| |____| |
_____ _____ ___________ ___________ ___ _____ _____ _____ _ _
/ __ \ _ || _ | ___ \ ___| ___ \/ _ \_ _|_ _| _ | \ | |
| / \/ | | || | | | |_/ / |__ | |_/ / /_\ \| | | | | | | | \| |
| | | | | || | | | __/| __|| /| _ || | | | | | | | . ` |
| \__/\ \_/ /\ \_/ / | | |___| |\ \| | | || | _| |_\ \_/ / |\ |
\____/\___/ \___/\_| \____/\_| \_\_| |_/\_/ \___/ \___/\_| \_/
to the misery of closed source software.