config/arch/powerpc.in
author Bart vdr. Meulen <bartvdrmeulen@gmail.com>
Mon Jul 19 23:16:02 2010 +0200 (2010-07-19)
branch1.7
changeset 2046 471acb219d77
parent 1345 27fec561af53
child 2112 0b83ab44a914
permissions -rw-r--r--
complibs: fix using static companion libraries

When building a cross-compiler for a target which uses a file extension for
binaries the symbolic link to cc is not created correctly because the lookup
of the gcc binary is done in a incorrect path

Signed-off-by: Bart vdr. Meulen <bartvdrmeulen@gmail.com>
(transplanted from 3917f2dafed1bb189e39f50e8506b3141926d7e1)
     1 # powerpc specific configuration file
     2 
     3 config ARCH_powerpc
     4     select ARCH_SUPPORTS_32
     5     select ARCH_SUPPORTS_64 if EXPERIMENTAL
     6     select ARCH_DEFAULT_32
     7     select ARCH_USE_MMU
     8     select ARCH_SUPPORT_ABI
     9     select ARCH_SUPPORT_CPU
    10     select ARCH_SUPPORT_TUNE
    11     help
    12       The PowerPC architecture, as defined by:
    13         http://www.ibm.com/developerworks/eserver/articles/archguide.html
    14 
    15 config ARCH_POWERPC_SPE
    16     bool
    17     prompt "Enable SPE support"
    18     default n
    19     help
    20       Add support for the Signal Processing Engine.  This will set up
    21       the toolchain so that it supports the SPE ABI extensions. This
    22       mainly targets Freescale e500 processors.
    23       
    24       Setting this option will append "spe" to the end of your target
    25       tuple name (e.g., powerpc-e500v2-linux-gnuspe) so that the gcc
    26       configure/build system will know to include SPE ABI support.
    27       It will also automatically add "-mabi=spe -mspe" to your
    28       TARGET_CFLAGS, and "--enable-e500_double" to your CC_EXTRA_CONFIG,
    29       so you do not need to explicitly add them.