cross compiling wind river linux for ppc architecture

[Paul Gortmaker]

On Tue, Aug 11, 2009 at 10:09 AM, Sridhar Mahadevan<msridhar87 at gmail.com> wrote:
> Hi,
> Am trying to compile my WRL 2.6.21 kernel for PPC architecture.
> The processor am using is AMCC powerpc 440EP .

This isn't really the best choice of forum for trying to get help like this.
Most of the people here are focused on working with the latest development
kernels, and won't have the time to go back and look at year-old kernels
based on the now removed PPC architecture.

Plus they won't necessarily have any knowledge of what the WRL specific
changes may or may not contain.  If you have the opportunity to do so,
the best choice for you would be to go through the normal WR support
channels with full details of your problem.

At a glance, it looks like you are trying to build with ARCH=powerpc, and
yet I don't think (from memory) that the 4xx boards had migrated from
ARCH=ppc until sometime around the 2.6.24-ish timeframe.

Paul.

> I just built the file system by running the configure command with
> --enable-rootfs=glibc-small and --enable-cpu-ppc-440 and i got a cross
> compiler.
> I took the linux kernel image and updated the PATH variable to the path of
> my cross compiler.I did a make with ARCH=powerpc and CROSS_COMPILER=/my
> cross compiler,except gcc/.
>
> When I try to do this I get the following error.
> arch/powerpc/mm/44x_mmu.c: In function 'mmu_mapin_ram':
> arch/powerpc/mm/44x_mmu.c:106: error: 'PPC_PIN_SIZE' undeclared (first use
> in this function)
> arch/powerpc/mm/44x_mmu.c:106: error: (Each undeclared identifier is
> reported only once
> arch/powerpc/mm/44x_mmu.c:106: error: for each function it appears in.)
> arch/powerpc/mm/44x_mmu.c:106: error: 'PPC44x_PIN_SHIFT' undeclared (first
> use in this function)
> arch/powerpc/mm/44x_mmu.c:109: error: 'PPC44x_LOW_SLOT' undeclared (first
> use in this function)
> make[1]: *** [arch/powerpc/mm/44x_mmu.o] Error 1
> make: *** [arch/powerpc/mm] Error 2
> It ll be very helpful for me if I could get a solution for this.
>
> Regards
> Sridhar M
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>