Re: [RTnet-developers] ppc/powerpc ambiguity while cross-compiling rtnet

[Wolfgang G. <wg...@gr...>]

Jan Kiszka wrote:
> Giammarco Zacheo wrote:
>> Hi,
>> while compiling rtnet 0.9.11 for a mpc5200-based (powerpc) board with
>> xenomai 2.4.8 on a denx-2.6.29.4 kernel, i had problems while running
>> the configure script, which wasn't able to find Xenomai headers in the
>> kernel tree. This is due to the fact that the configure script is
>> still looking for the arch/ppc obsoleted directory.
>>
>> The following patch worked for me, but I'm afraid this could break
>> compatibility with older kernels and/or RTAI/Xenomai releases. There's
>> probably a better way to do this. Any ideas?
>>
>> Cheers,
>> Giammarco
>>
>> --- a/configure.ac
>> +++ b/configure.ac
>> @@ -58,10 +58,14 @@ case "$host" in
>>         RTNET_TARGET_ARCH=arm
>>         wanted_kernel_arch=CONFIG_ARM
>>         ;;
>> -    powerpc-*|ppc-*)
>> +    ppc-*)
>>         RTNET_TARGET_ARCH=ppc
>>         wanted_kernel_arch=CONFIG_PPC
>>         ;;
>> +    powerpc-*)
>> +        RTNET_TARGET_ARCH=powerpc
>> +        wanted_kernel_arch=CONFIG_PPC
>> +        ;;
>> #    mips-*|mipsel-*)
>> #       RTNET_TARGET_ARCH=mips
>> #       wanted_kernel_arch=CONFIG_MIPS
>>
> 
> Wolfgang, can you check if it breaks anything (specifically 2.4)?

This does not work for Kernels using the arch/ppc tree. Retrieving the
real ARCH from $host (powerpc-unknown-linux-gnu in my case) gives always
"powerpc". Either we provide a configuration parameter "--arch=" or we
try to retrieve ARCH from the kernel tree, e.g. by checking "include/asm".

Wolfgang.