scripts: add "FILE" and "CFG" debug levels.
I ran into some minor difficulties looking through the build log for a
particular file: I wasn't interested in seeing it unpacked, but only
when it is built or installed. Adding these two levels allows me to
differentiate between those cases.
[Yann E. MORIN: Those are blind log levels, and are used only to search
in the build-log afterward.]
Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
1 # Compute ARM-specific values
3 CT_DoArchTupleValues() {
4 # The architecture part of the tuple:
5 CT_TARGET_ARCH="${CT_ARCH}${target_endian_eb}"
7 # The system part of the tuple:
8 case "${CT_LIBC},${CT_ARCH_ARM_EABI}" in
9 *glibc,y) CT_TARGET_SYS=gnueabi;;
10 uClibc,y) CT_TARGET_SYS=uclibcgnueabi;;
11 *,y) CT_TARGET_SYS=eabi;;
14 # Set the default instrcution set mode
15 case "${CT_ARCH_ARM_MODE}" in
18 CT_ARCH_CC_CORE_EXTRA_CONFIG="--with-mode=thumb"
19 CT_ARCH_CC_EXTRA_CONFIG="--with-mode=thumb"
20 # CT_ARCH_TARGET_CFLAGS="-mthumb"
24 if [ "${CT_ARCH_ARM_INTERWORKING}" = "y" ]; then
25 CT_ARCH_TARGET_CFLAGS+=" -mthumb-interwork"