ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2025-01-31 16:36:14 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Overide locale to C so as to have readable logs.

Browse Source 
Offer a DEBUG & EXPERIMENTAL setting to not overide locale.

 /trunk/scripts/crosstool.sh       |   10     7     3     0 +++++++---
 /trunk/config/global/ct-behave.in |   17    17     0     0 +++++++++++++++++
 2 files changed, 24 insertions(+), 3 deletions(-)
This commit is contained in:
Yann E. MORIN" 2008-11-20 17:48:10 +00:00
parent 8cd606ddc2
commit 42fe84cd15
2 changed files with 24 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
config/global/ct-behave.in
View File

@ -71,4 +71,21 @@ config DEBUG_CT_SAVE_STEPS_GZIP
further doesn't gain much, and takes far more time (believe me, I've
got figures here! :-) ).
config NO_OVERIDE_LC_MESSAGES
bool
prompt "Do *not* overide LC_MESSAGES (EXPERIMENTAL)"
depends on EXPERIMENTAL
default n
help
By default, crosstool-NG sets and exports LC_ALL=C so that the
build.log file contains english messages, that can be read by
people most likely to help interpret the logs. If you say N here,
and your locale is not an english language, then dissecting your
log file will be difficult for most people but you.
If you say Y here, then your current locale settings will be used
to print messages, instead of plain english.
Say N, please.
endif

10
scripts/crosstool.sh
View File

@ -20,13 +20,17 @@
# - initialise logging.
. "${CT_LIB_DIR}/scripts/functions"
CT_STAR_DATE=$(CT_DoDate +%s%N)
CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
# Parse the configuration file
# It has some info about the logging facility, so include it early
. .config
# Overide the locale early, in case we ever translate crosstool-NG messages
[ -z "${CT_NO_OVERIDE_LC_MESSAGES}" ] && export LC_ALL=C
# Start date. Can't be done until we know the locale
CT_STAR_DATE=$(CT_DoDate +%s%N)
CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
# Yes! We can do full logging from now on!
CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"