config/kernel/linux.in.2
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Wed Dec 05 20:31:43 2012 +0100 (2012-12-05)
changeset 3134 863723936e24
parent 2446 d902cd77419f
permissions -rw-r--r--
scripts/xldd: use user's sed and grep

xldd uses sed and grep as detected by ./configure. This works well if is
used on the machine that build the toolchain.

But if the user moves the toolchain to another machine where sed and grep
are not in the same directory (eg. /bin/sed vs. /usr/bin/sed), then xldd
will stop functionning.

Fix that by using ${SED} and ${GREP} if they are set in the environment.

Reported-by: Samuel Martin <s.martin49@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
     1 # Linux kernel options
     2 
     3 if ! KERNEL_LINUX_USE_CUSTOM_HEADERS
     4 
     5 choice
     6     bool
     7     prompt "Kernel verbosity:"
     8     default KERNEL_LINUX_VERBOSITY_0
     9 
    10 config KERNEL_LINUX_VERBOSITY_0
    11     bool
    12     prompt "Simplified"
    13     help
    14       Print simplified command lines.
    15 
    16 config KERNEL_LINUX_VERBOSITY_1
    17     bool
    18     prompt "Full commands"
    19     help
    20       Print full command lines.
    21 
    22 config KERNEL_LINUX_VERBOSITY_2
    23     bool
    24     prompt "Exec reasons"
    25     help
    26       Print the reasons why a make target is rebuild.
    27 
    28 endchoice
    29 
    30 config KERNEL_LINUX_VERBOSE_LEVEL
    31     int
    32     default 0 if KERNEL_LINUX_VERBOSITY_0
    33     default 1 if KERNEL_LINUX_VERBOSITY_1
    34     default 2 if KERNEL_LINUX_VERBOSITY_2
    35 
    36 config KERNEL_LINUX_INSTALL_CHECK
    37     bool
    38     prompt "Check installed headers"
    39     default y
    40     help
    41       If you are in doubt that installed headers are buggy, say 'Y'
    42       here to have an extra check passed onto the headers.
    43 
    44 endif # ! KERNEL_LINUX_USE_CUSTOM_HEADERS