powerpc-linux-gcc vs ppx_8xx-gcc and ppc_6xx-gcc

powerpc-linux-gcc vs ppx_8xx-gcc and ppc_6xx-gcc

[Lixin Yao]

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

Hello, All,

I use ELDK 4.2 to work on platforms, one with MPC860 and the other with
MPC8248.

In installation, I see links:
ppc_8xx-gcc -> ppc-linux-gcc
ppc_6xx-gcc -> ppc-linux-gcc
ppc-linux-gcc -> powerpc-linux-gcc

I understand ppc_8xx-gcc needs to be used for MPC860 and ppc_6xx-gcc
needs to be used for MPC8248. But both point to the same
"powerpc-linux-gcc". 

What are the differences between powerpc-linux-gcc, ppx_8xx-gcc and
ppc_6xx-gcc? What's the default target processorr of powerpc-linux-gcc?

Thanks.

Lixin Yao
Harris Strate Networks Inc.
RTP, North Carolina


[-- Attachment #2: Type: text/html, Size: 1454 bytes --]

Re: powerpc-linux-gcc vs ppx_8xx-gcc and ppc_6xx-gcc

[Wolfgang Denk]

Dear "Lixin Yao",

you should ask ELDK related questions on the ELDK mailing list, see
http://lists.denx.de/mailman/listinfo/eldk

In message <03D77CA4AC7F4D48A6AB5DA3F1001B3FB5BAC7@exchtxus2.HSTX.global.vpn> you wrote:
> 
> I use ELDK 4.2 to work on platforms, one with MPC860 and the other with
> MPC8248.
> 
> In installation, I see links:
> ppc_8xx-gcc -> ppc-linux-gcc
> ppc_6xx-gcc -> ppc-linux-gcc
> ppc-linux-gcc -> powerpc-linux-gcc
>
> I understand ppc_8xx-gcc needs to be used for MPC860 and ppc_6xx-gcc
> needs to be used for MPC8248. But both point to the same
> "powerpc-linux-gcc". 
>
> What are the differences between powerpc-linux-gcc, ppx_8xx-gcc and
> ppc_6xx-gcc? What's the default target processorr of powerpc-linux-gcc?

You must always specify the wanted target architecture in the
CROSS_COMPILE environment variable. If you run ppc_6xx-gcc or
powerpc-linux-gcc (which is possible, but NOT recommended because
it's often difficult to detect misconfigurations like incorrect
CROSS_COMPILE settings) then the target architecture is taken from
the CROSS_COMPILE value.

It is recommended to set CROSS_COMPILE and then run
${CROSS_COMPILE}gcc because this allows easy switching between
different target architectures, i. e. you can write Makefiles that
work both natively and for cross development, and for any of the
supported target architectures without changes to the code.

See for example the Linux or U-Boot Makefiles which work this way.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Success covers a multitude of blunders."       - George Bernard Shaw