Yes it is.

Giammarco

On Fri, Jul 3, 2009 at 12:42 PM, Wolfgang Grandegger<[email protected]> wrote:
> Wolfgang Grandegger wrote:
>> 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".
>
> Giammarco, does the patch below work for you?
>
> Wolfgang.
>
> ---
>  configure.ac |    9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
>
> Index: rtnet/configure.ac
> ===================================================================
> --- rtnet.orig/configure.ac
> +++ rtnet/configure.ac
> @@ -59,7 +59,7 @@ case "$host" in
>         wanted_kernel_arch=CONFIG_ARM
>         ;;
>     powerpc-*|ppc-*)
> -        RTNET_TARGET_ARCH=ppc
> +        RTNET_TARGET_ARCH=powerpc
>         wanted_kernel_arch=CONFIG_PPC
>         ;;
>  #    mips-*|mipsel-*)
> @@ -225,6 +225,13 @@ else
>     AC_MSG_RESULT([$RTEXT_LINUX_DIR (kernel 
> ${RTEXT_LINUX_VERSION}${CONFIG_SMP:+-SMP} + Xenomai)])
>  fi
>
> +# Fixup real arch for powerpc
> +if test "${RTNET_TARGET_ARCH}" = "powerpc" ; then
> +   AC_MSG_CHECKING([for real PowerPC arch])
> +    readlink ${CONFIG_RTNET_LINUX_DIR}/include/asm | grep -q ppc && 
> RTNET_TARGET_ARCH="ppc"
> +    AC_MSG_RESULT([$RTNET_TARGET_ARCH])
> +fi
> +
>  #
>  # from now we think we've found some RT-extension, so if we got an error
>  # it will be fatal, thus exit with AC_MSG_ERROR
>
>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have 
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
RTnet-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rtnet-developers

Reply via email to