arch/sh/config.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Tue Sep 23 14:48:10 2008 +0000 (2008-09-23)
changeset 872 fd4bf138f08f
parent 628 87802cb25a0f
child 891 4d770d1f65a0
permissions -rw-r--r--
Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.

/trunk/scripts/build/libc/glibc.sh | 14 2 12 0 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
     1 # Super-H specific configuration file
     2 
     3 config ARCH_sh
     4     select ARCH_SUPPORTS_BOTH_ENDIAN
     5     select ARCH_DEFAULT_LE
     6     help
     7       The Super-H architecture, as defined by:
     8         http://www.renesas.com/fmwk.jsp?cnt=superh_family_landing.jsp&fp=/products/mpumcu/superh_family/
     9 
    10 choice
    11     bool
    12     prompt "Variant"
    13 
    14 config ARCH_SH_SH3
    15     bool
    16     prompt "sh3"
    17 
    18 config ARCH_SH_SH4
    19     bool
    20     prompt "sh4"
    21 
    22 config ARCH_SH_SH4A
    23     bool
    24     prompt "sh4a"
    25 
    26 endchoice
    27 
    28 config ARCH_SH_VARIANT
    29     string
    30     default "sh3"   if ARCH_SH_SH3
    31     default "sh4"   if ARCH_SH_SH4
    32     default "sh4a"  if ARCH_SH_SH4A