This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Unfortunately, I can't do that - it is part of the process I need to follow - build a 'pure' GCC compiler which then builds my software without relying on the host environment (or at least relying on it as little as possible). I know that I could just transfer the GCC files/binaries from the host environment onto my source tree and do the rest, but that is not an option for me.1. Does that mean that I should follow the steps in the previous
section ("Building a native compiler"), use the 3-stage bootstrapping
and after this use the resulting compiler to build another GCC cross
compiler (including the appropriate toolchain) for the 3 architectures
I am interested in and use this compiler to build my software?
Yes. Actually most people just skip the step of building the native
compiler, and just use the native compiler they have installed anyhow.
That will normally work fine.
I meant (but it seems I haven't explained it properly) GCC No 3 as I pointed out above.3. If that is the case what steps should I use to build the GCC
compiler for the target image architectures (powerpc and i586/i686)?
Here you are building a cross compiler. I'm not sure what you are
asking, exactly. You use --target when you run configure as described
in the documentation.
Brilliant guidance that - yes, I see "native" as in for the host environment, so I slightly messed these terms up I see.5. I assume at the end of this process I will end up with my native
cross compiler which I could then use to build my software. Do I need
to do anything else?
The words "native cross compiler" don't mean anything to me. I would say that you have a cross-compiler which runs on your build system.
6. Also, later in that section I am advised that for building the
binutils (which I would need to anyway!) I need to use the same --host
and --target that are used for configuring GCC, but which one - the
native cross-compiling GCC or the one that helped build it?
The cross-compiler.
It may help you to glance at
http://www.airs.com/ian/configure/configure_5.html#SEC29
to understand the terminology we use.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |