config/global/logging.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Jul 13 10:32:38 2008 +0000 (2008-07-13)
changeset 645 8e58024f8e37
parent 445 17aa08b441f2
child 753 53a577cbd9d4
permissions -rw-r--r--
Ioannis E. VENETIS <venetis@mail.capsl.udel.edu> pointed out that GMP and MPFR were not used by gcc.
Turned out that none could use GMP and MPFR as the config option changed its name, but the change was not propagated to all users.

/trunk/scripts/build/binutils.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/300-gdb.sh | 2 1 1 0 +-
/trunk/scripts/build/cc_gcc.sh | 6 3 3 0 +++---
3 files changed, 5 insertions(+), 5 deletions(-)
yann@445
     1
# Options specific to logging
yann@244
     2
yann@1
     3
comment "Logging"
yann@1
     4
yann@1
     5
choice
yann@1
     6
    bool
yann@1
     7
    prompt "Maximum log level to see:"
yann@252
     8
    default LOG_INFO if !DEBUG_CT
yann@252
     9
    default LOG_DEBUG if DEBUG_CT
yann@1
    10
yann@1
    11
config LOG_ERROR
yann@1
    12
    bool
yann@1
    13
    prompt "ERROR"
yann@1
    14
    help
yann@1
    15
      The build will be silent.
yann@174
    16
      Only if there is an error will you see a message.
yann@1
    17
yann@1
    18
config LOG_WARN
yann@1
    19
    bool
yann@1
    20
    prompt "WARN"
yann@1
    21
    help
yann@1
    22
      The same as above, plus warnings.
yann@1
    23
yann@1
    24
config LOG_INFO
yann@1
    25
    bool
yann@1
    26
    prompt "INFO"
yann@1
    27
    help
yann@1
    28
      The same as above, plus informational messages (main steps).
yann@1
    29
yann@1
    30
config LOG_EXTRA
yann@1
    31
    bool
yann@1
    32
    prompt "EXTRA"
yann@1
    33
    help
yann@1
    34
      The same as above, plus extra messages (sub-steps).
yann@1
    35
yann@1
    36
config LOG_DEBUG
yann@1
    37
    bool
yann@1
    38
    prompt "DEBUG"
yann@1
    39
    help
yann@78
    40
      The same as above, plus lots of crosstool-NG debug information.
yann@78
    41
yann@78
    42
config LOG_ALL
yann@78
    43
    bool
yann@78
    44
    prompt "ALL"
yann@78
    45
    help
yann@78
    46
      The same as above, plus all components build messages (very noisy!).
yann@1
    47
yann@1
    48
endchoice
yann@1
    49
yann@1
    50
config LOG_LEVEL_MAX
yann@1
    51
    string
yann@1
    52
    default "ERROR"   if LOG_ERROR
yann@1
    53
    default "WARN"    if LOG_WARN
yann@1
    54
    default "INFO"    if LOG_INFO
yann@1
    55
    default "EXTRA"   if LOG_EXTRA
yann@1
    56
    default "DEBUG"   if LOG_DEBUG
yann@78
    57
    default "ALL"     if LOG_ALL
yann@1
    58
yann@47
    59
config LOG_SEE_TOOLS_WARN
yann@47
    60
    bool
yann@174
    61
    prompt "Warnings from the tools' builds"
yann@47
    62
    default n
yann@47
    63
    depends on ! LOG_ERROR
yann@47
    64
    help
yann@197
    65
      Treat warnings from the different tools as crosstool-NG warnings.
yann@108
    66
      If you say 'y' here, then those warnings will be prefixed with
yann@108
    67
      '[WARN ]' instead of the default '[ALL  ]'.
yann@47
    68
yann@108
    69
      You can safely say 'n' here. Those warnings will anyway be
yann@108
    70
      recorded in the log file (provided you configured one).
yann@47
    71
yann@197
    72
      Tools error will always be logged as crosstool-NG errors.
yann@174
    73
yann@1
    74
config LOG_PROGRESS_BAR
yann@1
    75
    bool
yann@1
    76
    prompt "Progress bar"
yann@173
    77
    default y
yann@78
    78
    depends on ! LOG_ALL
yann@1
    79
    help
yann@112
    80
      If you say 'y' here, you'll be able to see the elapsed time.
yann@1
    81
      
yann@112
    82
      As a bonus, you'll also get a rotating bar (/-\|) showing you
yann@112
    83
      that the build is not stalled (the bar rotates 1/4 every 10 lines
yann@112
    84
      of components build log).
yann@112
    85
yann@112
    86
      Note that the elapsed time can stall for a little while if a
yann@112
    87
      component has long commands, as the elapsed time is only updated
yann@112
    88
      each line.
yann@1
    89
yann@1
    90
config LOG_TO_FILE
yann@1
    91
    bool
yann@1
    92
    prompt "Log to a file"
yann@1
    93
    default y
yann@1
    94
    help
yann@1
    95
      Save *full* logs to a file. Even log levels you didn't specify above
yann@174
    96
      will be available in this file. The log file will be named build.log
yann@174
    97
      and stored in the toolchain prefix dir (set above).
yann@1
    98
yann@47
    99
      As a bonus, there is a script in tools/extractConfig.sh that is able
yann@47
   100
      to extract the configuration of crosstool-NG from the log file.
yann@47
   101
yann@47
   102
      Definitely, say Y.
yann@47
   103
yann@174
   104
config LOG_FILE_COMPRESS
yann@174
   105
    bool
yann@174
   106
    prompt "Compress the log file"
yann@174
   107
    default n
yann@1
   108
    depends on LOG_TO_FILE
yann@1
   109
    help
yann@174
   110
      Compress the log file once the toolchain is successfully built.