This is the mail archive of the
mailing list for the GCC project.
Re: Exhaustive Instructions for Toolchain Generation
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: R0b0t1 <r030t1 at gmail dot com>
- Cc: GCC Development <gcc at gcc dot gnu dot org>
- Date: Tue, 26 Sep 2017 22:30:07 +0100
- Subject: Re: Exhaustive Instructions for Toolchain Generation
- Authentication-results: sourceware.org; auth=none
- References: <CAAD4mYhF0JAkvLcBzHCocB9L5iTd5XU9K33WHeDsJo=_GxqfLg@mail.gmail.com>
On 26 September 2017 at 22:05, R0b0t1 <email@example.com> 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.)
What does "knowing all options which must be configured" mean?
Must be configured for what?
> 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.
https://gcc.gnu.org/install/prerequisites.html should be clear.
isl is optional, it's not required. expat is not needed. zlib is not
needed, because the source for it is included in the GCC tree.
> 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 targets?
Read the docs.