scripts/crosstool-NG.sh.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Jan 10 23:09:38 2013 +0100 (2013-01-10)
changeset 3164 5a534736f62f
parent 3163 06938bc1c6e7
child 3172 edb17e96ca60
permissions -rw-r--r--
scripts: woops, root's UID is 0, not 1000!

Left-over from a test... :-(

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
yann@1156
     1
#!@@CT_bash@@
yann@1
     2
# Copyright 2007 Yann E. MORIN
yann@1
     3
# Licensed under the GPL v2. See COPYING in the root of this package.
yann@1
     4
yann@1
     5
# This is the main entry point to crosstool
yann@1
     6
# This will:
yann@1
     7
#   - download, extract and patch the toolchain components
yann@1
     8
#   - build and install each components in turn
yann@1
     9
#   - and eventually test the resulting toolchain
yann@1
    10
yann@1
    11
# What this file does is prepare the environment, based upon the user-choosen
yann@1
    12
# options. It also checks the existing environment for un-friendly variables,
yann@96
    13
# and builds the tools.
yann@1
    14
yann@1
    15
# Parse the common functions
yann@501
    16
# Note: some initialisation and sanitizing is done while parsing this file,
yann@501
    17
# most notably:
yann@501
    18
#  - set trap handler on errors,
yann@501
    19
#  - don't hash commands lookups,
yann@501
    20
#  - initialise logging.
yann@182
    21
. "${CT_LIB_DIR}/scripts/functions"
yann@1
    22
yann@1
    23
# Parse the configuration file
yann@96
    24
# It has some info about the logging facility, so include it early
yann@2468
    25
. .config.2
yann@1156
    26
# Yes! We can do full logging from now on!
yann@1
    27
yann@3163
    28
# Check running as root
yann@3163
    29
if [ -z "${CT_ALLOW_BUILD_AS_ROOT_SURE}" ]; then
yann@3164
    30
    if [ $(id -u) -eq 0 ]; then
yann@3163
    31
        CT_DoLog ERROR "You must NOT be root to run crosstool-NG"
yann@3163
    32
        exit 1
yann@3163
    33
    fi
yann@3163
    34
fi
yann@3163
    35
yann@3083
    36
# If we want an interactive debug-shell, we must ensure these FDs
yann@3083
    37
# are indeed connected to a terminal (and not redirected in any way).
yann@3083
    38
if [ "${CT_DEBUG_INTERACTIVE}" = "y" -a ! \( -t 0 -a -t 6 -a -t 2 \) ]; then
yann@3083
    39
    CT_DoLog ERROR "Can't spawn interactive debug-shell,"
yann@3083
    40
    CT_DoLog ERROR "because stdout/stderr has been redirected."
yann@3083
    41
    exit 1
yann@3083
    42
fi
yann@3083
    43
antony@2564
    44
# Override the locale early, in case we ever translate crosstool-NG messages
yann@2171
    45
if [ -z "${CT_NO_OVERIDE_LC_MESSAGES}" ]; then
yann@2171
    46
    export LC_ALL=C
yann@2171
    47
    export LANG=C
yann@2171
    48
fi
yann@1064
    49
js@2044
    50
# remove . from PATH since it can cause gcc build failures
js@2044
    51
CT_SanitizePath
js@2044
    52
yann@1416
    53
# Some sanity checks in the environment and needed tools
yann@1416
    54
CT_DoLog INFO "Performing some trivial sanity checks"
yann@1416
    55
CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
yann@3063
    56
CT_TestAndAbort "Don't set LIBRARY_PATH. It screws up the build." -n "${LIBRARY_PATH}"
yann@3063
    57
CT_TestAndAbort "Don't set LPATH. It screws up the build." -n "${LPATH}"
yann@1416
    58
CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
yann@1416
    59
CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
yann@1416
    60
CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
yann@1416
    61
export GREP_OPTIONS=
yann@2801
    62
# Workaround against openSUSE 12.1 that breaks ./configure for cross-compilation:
yann@2801
    63
export CONFIG_SITE=
yann@1416
    64
yann@1416
    65
# Some sanity checks on paths content
yann@1416
    66
for d in            \
yann@1416
    67
    LOCAL_TARBALLS  \
yann@1416
    68
    WORK            \
yann@1416
    69
    PREFIX          \
yann@1416
    70
    INSTALL         \
yann@1416
    71
    ; do
yann@1416
    72
        eval dir="\${CT_${d}_DIR}"
yann@1416
    73
        case "${dir}" in
yann@1416
    74
            *" "*)
yann@1416
    75
                CT_Abort "'CT_${d}_DIR'='${dir}' contains a space in it.\nDon't use spaces in paths, it breaks things."
yann@1416
    76
                ;;
daniel@3125
    77
            *:*)
daniel@3125
    78
                CT_Abort "'CT_${d}_DIR'='${dir}' contains a colon in it.\nDon't use colons in paths, it breaks things."
daniel@3125
    79
                ;;
yann@1416
    80
        esac
yann@1416
    81
done
yann@1416
    82
yann@1156
    83
# Where will we work?
yann@3081
    84
CT_WORK_DIR="${CT_WORK_DIR:-${CT_TOP_DIR}/.build}"
yann@1270
    85
CT_DoExecLog ALL mkdir -p "${CT_WORK_DIR}"
js@3082
    86
CT_DoExecLog DEBUG rm -f "${CT_WORK_DIR}/backtrace"
yann@1270
    87
yann@1270
    88
# Check build file system case-sensitiveness
yann@1278
    89
CT_DoExecLog DEBUG touch "${CT_WORK_DIR}/foo"
yann@1270
    90
CT_TestAndAbort "Your file system in '${CT_WORK_DIR}' is *not* case-sensitive!" -f "${CT_WORK_DIR}/FOO"
yann@1278
    91
CT_DoExecLog DEBUG rm -f "${CT_WORK_DIR}/foo"
yann@1156
    92
yann@1444
    93
# Check the user is using an existing SHELL to be used by ./configure and Makefiles
yann@2705
    94
CT_TestOrAbort "The CONFIG_SHELL '${CT_CONFIG_SHELL}' is not valid" -f "${CT_CONFIG_SHELL}" -a -x "${CT_CONFIG_SHELL}"
yann@1421
    95
antony@2564
    96
# Create the bin-override early
yann@1219
    97
# Contains symlinks to the tools found by ./configure
yann@1156
    98
# Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so
yann@1156
    99
# they can be safely used
richard@1726
   100
CT_TOOLS_OVERIDE_DIR="${CT_WORK_DIR}/tools"
antony@2564
   101
CT_DoLog DEBUG "Creating bin-override for tools in '${CT_TOOLS_OVERIDE_DIR}'"
richard@1726
   102
CT_DoExecLog DEBUG mkdir -p "${CT_TOOLS_OVERIDE_DIR}/bin"
yann@2838
   103
cat "${CT_LIB_DIR}/paths.sh" |while read trash line; do
yann@1156
   104
    tool="${line%%=*}"
yann@1156
   105
    path="${line#*=}"
yann@1517
   106
    CT_DoLog DEBUG "Creating script-override for '${tool}' -> '${path}'"
yann@2838
   107
    # Note: we need to supress the " in the path because
yann@2838
   108
    # there can be arguments in there (thanks autostuff...)
yann@2838
   109
    printf "#${BANG}${CT_CONFIG_SHELL}\nexec ${path//\"/} \"\${@}\"\n" >"${CT_TOOLS_OVERIDE_DIR}/bin/${tool}"
richard@1726
   110
    CT_DoExecLog ALL chmod 700 "${CT_TOOLS_OVERIDE_DIR}/bin/${tool}"
yann@1156
   111
done
richard@1726
   112
export PATH="${CT_TOOLS_OVERIDE_DIR}/bin:${PATH}"
yann@1156
   113
yann@1064
   114
# Start date. Can't be done until we know the locale
yann@1416
   115
# Also requires the bin-override tools
yann@1064
   116
CT_STAR_DATE=$(CT_DoDate +%s%N)
yann@1064
   117
CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
yann@1064
   118
yann@1156
   119
# Log real begining of build, now
yann@379
   120
CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
yann@379
   121
yann@2468
   122
# We really need to extract from ,config and not .config.2, as we
yann@2468
   123
# do want the kconfig's values, not our mangled config with arrays.
yann@894
   124
CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
yann@1247
   125
CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
yann@96
   126
CT_EndStep
yann@63
   127
yann@290
   128
CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
yann@290
   129
unset MAKEFLAGS
yann@290
   130
export MAKEFLAGS
yann@290
   131
yann@1
   132
CT_DoLog INFO "Building environment variables"
yann@1
   133
yann@965
   134
# Include sub-scripts instead of calling them: that way, we do not have to
yann@965
   135
# export any variable, nor re-parse the configuration and functions files.
yann@1225
   136
. "${CT_LIB_DIR}/scripts/build/internals.sh"
yann@903
   137
. "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
richard@1727
   138
. "${CT_LIB_DIR}/scripts/build/companion_tools.sh"
yann@965
   139
. "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
Yann@3115
   140
. "${CT_LIB_DIR}/scripts/build/companion_libs.sh"
diorcet@3123
   141
. "${CT_LIB_DIR}/scripts/build/binutils/${CT_BINUTILS}.sh"
yann@965
   142
. "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
yann@965
   143
. "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
yann@965
   144
. "${CT_LIB_DIR}/scripts/build/debug.sh"
mgl@1965
   145
. "${CT_LIB_DIR}/scripts/build/test_suite.sh"
yann@380
   146
yann@335
   147
# Target tuple: CT_TARGET needs a little love:
yann@335
   148
CT_DoBuildTargetTuple
yann@1
   149
yann@96
   150
# Kludge: If any of the configured options needs CT_TARGET,
yann@96
   151
# then rescan the options file now:
yann@2468
   152
. .config.2
yann@96
   153
yann@1663
   154
# Sanity check some directories
yann@1663
   155
CT_TestAndAbort "'CT_PREFIX_DIR' is not set: where should I install?" -z "${CT_PREFIX_DIR}"
yann@1663
   156
yann@397
   157
# Second kludge: merge user-supplied target CFLAGS with architecture-provided
yann@531
   158
# target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
yann@531
   159
# Put user-supplied flags at the end, so that they take precedence.
yann@397
   160
CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
yann@531
   161
CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
yann@2467
   162
CT_CC_CORE_EXTRA_CONFIG_ARRAY=( ${CT_ARCH_CC_CORE_EXTRA_CONFIG} "${CT_CC_CORE_EXTRA_CONFIG_ARRAY[@]}" )
yann@2467
   163
CT_CC_EXTRA_CONFIG_ARRAY=( ${CT_ARCH_CC_EXTRA_CONFIG} "${CT_CC_EXTRA_CONFIG_ARRAY[@]}" )
yann@397
   164
benoit@2503
   165
# Compute the package version string
benoit@2503
   166
CT_PKGVERSION="crosstool-NG ${CT_VERSION}${CT_TOOLCHAIN_PKGVERSION:+ - ${CT_TOOLCHAIN_PKGVERSION}}"
benoit@2503
   167
yann@1416
   168
# Compute the working directories names
yann@610
   169
CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
yann@610
   170
CT_SRC_DIR="${CT_WORK_DIR}/src"
yann@610
   171
CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
yann@2308
   172
CT_BUILDTOOLS_PREFIX_DIR="${CT_WORK_DIR}/${CT_TARGET}/buildtools"
yann@1272
   173
CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
yann@1272
   174
CT_CONFIG_DIR="${CT_BUILD_DIR}/configs"
yann@2931
   175
# Note about HOST_COMPLIBS_DIR: it's always gonna be in the buildtools dir, or a
yann@2931
   176
# sub-dir. So we won't have to save/restore it, not even create it.
yann@2931
   177
# In case of cross or native, host-complibs are used for build-complibs;
yann@2931
   178
# in case of canadian or cross-native, host-complibs are specific
yann@2931
   179
case "${CT_TOOLCHAIN_TYPE}" in
yann@2931
   180
    native|cross)
yann@2931
   181
        CT_HOST_COMPLIBS_DIR="${CT_BUILDTOOLS_PREFIX_DIR}"
yann@2931
   182
        ;;
yann@2931
   183
    canadian|cross-native)
yann@2931
   184
        CT_HOST_COMPLIBS_DIR="${CT_BUILDTOOLS_PREFIX_DIR}/complibs-host"
yann@2931
   185
        ;;
yann@2931
   186
esac
yann@1272
   187
mgl@1965
   188
# Compute test suite install directory
mgl@1965
   189
CT_TEST_SUITE_DIR=${CT_INSTALL_DIR}/test-suite
mgl@1965
   190
yann@143
   191
# We must ensure that we can restart if asked for!
yann@143
   192
if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}"  ]; then
yann@143
   193
    CT_DoLog ERROR "You asked to restart a non-restartable build"
yann@143
   194
    CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
yann@153
   195
    CT_DoLog ERROR "in the config options for the previous build, or the state"
yann@425
   196
    CT_DoLog ERROR "directory for the previous build was deleted."
yann@143
   197
    CT_Abort "I will stop here to avoid any carnage"
yann@143
   198
fi
yann@143
   199
yann@403
   200
# If the local tarball directory does not exist, say so, and don't try to save there!
yann@1662
   201
if [    "${CT_SAVE_TARBALLS}" = "y"     \
yann@1662
   202
     -a ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
yann@1662
   203
    CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist."
yann@1662
   204
    CT_DoLog WARN "Will not save downloaded tarballs to local storage."
yann@523
   205
    CT_SAVE_TARBALLS=
yann@403
   206
fi
yann@403
   207
yann@85
   208
# Check now if we can write to the destination directory:
yann@85
   209
if [ -d "${CT_INSTALL_DIR}" ]; then
yann@523
   210
    CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
yann@85
   211
fi
yann@85
   212
yann@96
   213
# Good, now grab a bit of informations on the system we're being run on,
yann@96
   214
# just in case something goes awok, and it's not our fault:
yann@523
   215
CT_SYS_USER=$(id -un)
yann@523
   216
CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
yann@96
   217
# Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
yann@523
   218
CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
yann@523
   219
CT_SYS_KERNEL=$(uname -s)
yann@523
   220
CT_SYS_REVISION=$(uname -r)
titus@1954
   221
CT_SYS_OS=$(uname -s)
yann@523
   222
CT_SYS_MACHINE=$(uname -m)
yann@523
   223
CT_SYS_PROCESSOR=$(uname -p)
yann@523
   224
CT_SYS_GCC=$(gcc -dumpversion)
yann@523
   225
CT_SYS_TARGET=$(CT_DoConfigGuess)
yann@96
   226
CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
yann@96
   227
yann@96
   228
CT_DoLog EXTRA "Preparing working directories"
yann@96
   229
yann@121
   230
# Ah! The build directory shall be eradicated, even if we restart!
yann@2543
   231
# Ditto for the build tools install dir
yann@2543
   232
CT_DoForceRmdir "${CT_BUILD_DIR}" "${CT_BUILDTOOLS_PREFIX_DIR}"
yann@121
   233
yann@121
   234
# Don't eradicate directories if we need to restart
yann@121
   235
if [ -z "${CT_RESTART}" ]; then
yann@121
   236
    # Get rid of pre-existing installed toolchain and previous build directories.
yann@121
   237
    if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
yann@1138
   238
        CT_DoForceRmdir "${CT_TARBALLS_DIR}"
yann@121
   239
    fi
yann@121
   240
    if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
yann@1138
   241
        CT_DoForceRmdir "${CT_SRC_DIR}"
yann@121
   242
    fi
yann@2284
   243
    if [ -d "${CT_INSTALL_DIR}" -a "${CT_RM_RF_PREFIX_DIR}" = "y" ]; then
yann@1138
   244
        CT_DoForceRmdir "${CT_INSTALL_DIR}"
yann@121
   245
    fi
yann@121
   246
    # In case we start anew, get rid of the previously saved state directory
yann@121
   247
    if [ -d "${CT_STATE_DIR}" ]; then
yann@1138
   248
        CT_DoForceRmdir "${CT_STATE_DIR}"
yann@121
   249
    fi
yann@96
   250
fi
yann@85
   251
yann@121
   252
# Create the directories we'll use, even if restarting: it does no harm to
yann@121
   253
# create already existent directories, and CT_BUILD_DIR needs to be created
yann@121
   254
# anyway
yann@1135
   255
CT_DoExecLog ALL mkdir -p "${CT_TARBALLS_DIR}"
yann@1135
   256
CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
yann@1135
   257
CT_DoExecLog ALL mkdir -p "${CT_BUILD_DIR}"
yann@2308
   258
CT_DoExecLog ALL mkdir -p "${CT_BUILDTOOLS_PREFIX_DIR}/bin"
yann@1272
   259
CT_DoExecLog ALL mkdir -p "${CT_CONFIG_DIR}"
yann@1135
   260
CT_DoExecLog ALL mkdir -p "${CT_INSTALL_DIR}"
yann@1135
   261
CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}"
yann@2931
   262
CT_DoExecLog ALL mkdir -p "${CT_HOST_COMPLIBS_DIR}"
yann@1272
   263
yann@1272
   264
# Only create the state dir if asked for a restartable build
yann@1272
   265
[ -n "${CT_DEBUG_CT_SAVE_STEPS}" ] && CT_DoExecLog ALL mkdir -p "${CT_STATE_DIR}"
yann@121
   266
yann@1270
   267
# Check install file system case-sensitiveness
yann@1278
   268
CT_DoExecLog DEBUG touch "${CT_PREFIX_DIR}/foo"
yann@1270
   269
CT_TestAndAbort "Your file system in '${CT_PREFIX_DIR}' is *not* case-sensitive!" -f "${CT_PREFIX_DIR}/FOO"
yann@1278
   270
CT_DoExecLog DEBUG rm -f "${CT_PREFIX_DIR}/foo"
yann@1270
   271
yann@121
   272
# Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
yann@2339
   273
# the previous build was successful.
yann@1135
   274
CT_DoExecLog ALL chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
yann@85
   275
yann@397
   276
# Setting up the rest of the environment only if not restarting
yann@121
   277
if [ -z "${CT_RESTART}" ]; then
yann@2279
   278
    case "${CT_SYSROOT_NAME}" in
yann@2279
   279
        "")     CT_SYSROOT_NAME="sysroot";;
yann@2279
   280
        .)      CT_Abort "Sysroot name is set to '.' which is forbidden";;
yann@2279
   281
        *' '*)  CT_Abort "Sysroot name contains forbidden space(s): '${CT_SYSROOT_NAME}'";;
yann@2279
   282
        */*)    CT_Abort "Sysroot name contains forbidden slash(es): '${CT_SYSROOT_NAME}'";;
yann@2279
   283
    esac
yann@2279
   284
yann@2279
   285
    # Arrange paths depending on wether we use sysroot or not.
yann@121
   286
    if [ "${CT_USE_SYSROOT}" = "y" ]; then
yann@2653
   287
        CT_SYSROOT_REL_DIR="${CT_SYSROOT_DIR_PREFIX:+${CT_SYSROOT_DIR_PREFIX}/}${CT_SYSROOT_NAME}"
yann@2286
   288
        CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_REL_DIR}"
yann@1219
   289
        CT_DEBUGROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/debug-root"
yann@121
   290
        CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
yann@2286
   291
        CT_SanitiseVarDir CT_SYSROOT_REL_DIR CT_SYSROOT_DIR CT_DEBUGROOT_DIR CT_HEADERS_DIR 
yann@121
   292
        BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   293
        CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   294
        CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   295
        LIBC_SYSROOT_ARG=""
yann@121
   296
        # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
yann@121
   297
        # confused when $sysroot/usr/include is not present.
yann@121
   298
        # Note: --prefix=/usr is magic!
yann@121
   299
        # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
yann@121
   300
    else
yann@121
   301
        # plain old way. All libraries in prefix/target/lib
yann@121
   302
        CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
yann@1419
   303
        CT_DEBUGROOT_DIR="${CT_SYSROOT_DIR}"
yann@121
   304
        CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
yann@2280
   305
        CT_SanitiseVarDir CT_SYSROOT_DIR CT_DEBUGROOT_DIR CT_HEADERS_DIR 
yann@121
   306
        # hack!  Always use --with-sysroot for binutils.
yann@121
   307
        # binutils 2.14 and later obey it, older binutils ignore it.
yann@121
   308
        # Lets you build a working 32->64 bit cross gcc
yann@121
   309
        BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   310
        # Use --with-headers, else final gcc will define disable_glibc while
yann@121
   311
        # building libgcc, and you'll have no profiling
yann@121
   312
        CC_CORE_SYSROOT_ARG="--without-headers"
yann@121
   313
        CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
yann@121
   314
        LIBC_SYSROOT_ARG="prefix="
yann@121
   315
    fi
yann@1219
   316
    CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}"
yann@1219
   317
    CT_DoExecLog ALL mkdir -p "${CT_DEBUGROOT_DIR}"
yann@121
   318
yann@121
   319
    # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
yann@1180
   320
    # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail
yann@1180
   321
    # with: "ld: cannot open crti.o: No such file or directory"
yann@1180
   322
    # Also prepare the lib directory in the install dir, else some 64 bit archs
yann@1180
   323
    # won't build
yann@1180
   324
    CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/lib"
yann@1135
   325
    CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/lib"
yann@1135
   326
    CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
zhenqiang@2796
   327
    CT_DoExecLog ALL mkdir -p "${CT_HEADERS_DIR}"
yann@121
   328
yann@1420
   329
    if [ "${CT_USE_SYSROOT}" = "y" ]; then
yann@2279
   330
        # Prevent gcc from installing its libraries outside of the sysroot
yann@2653
   331
        CT_Pushd "${CT_PREFIX_DIR}/${CT_TARGET}"
yann@2653
   332
        CT_DoExecLog ALL ln -sf "${CT_SYSROOT_REL_DIR}/lib" "lib"
yann@2653
   333
        CT_Popd
yann@1420
   334
    fi
yann@740
   335
anthony@2138
   336
    # Since we're *not* multilib on the target side, we want all the
anthony@2138
   337
    # libraries to end up in "lib".  We create "lib64" (for 64-bit
anthony@2138
   338
    # build or host architectures) and "lib32" (for 32-bit emulation
anthony@2138
   339
    # on 64-bit) as symlinks to "lib".
anthony@2138
   340
    #
anthony@2138
   341
    # Not all of these symlinks are necessary, but better safe than
anthony@2138
   342
    # sorry. They are summarily removed by build/internals.sh:do_finish.
anthony@2138
   343
    for d in                            \
anthony@2138
   344
        "${CT_PREFIX_DIR}"              \
anthony@2138
   345
        "${CT_SYSROOT_DIR}"             \
anthony@2138
   346
        "${CT_SYSROOT_DIR}/usr"         \
anthony@2138
   347
        "${CT_PREFIX_DIR}/${CT_TARGET}" \
anthony@2138
   348
    ; do
anthony@2138
   349
        CT_DoExecLog ALL ln -sf "lib" "${d}/lib32"
anthony@2138
   350
        CT_DoExecLog ALL ln -sf "lib" "${d}/lib64"
anthony@2138
   351
    done
yann@740
   352
yann@1041
   353
    # Determine build system if not set by the user
titus@1958
   354
    if [ -z "${CT_BUILD}" ]; then
titus@1958
   355
        CT_BUILD=$(CT_DoConfigGuess)
titus@1958
   356
    fi
yann@121
   357
yann@1083
   358
    # Prepare mangling patterns to later modify BUILD and HOST (see below)
yann@1041
   359
    case "${CT_TOOLCHAIN_TYPE}" in
yann@1041
   360
        cross)
yann@1426
   361
            # A cross-compiler runs on the same machine it is built on
yann@1041
   362
            CT_HOST="${CT_BUILD}"
yann@1041
   363
            build_mangle="build_"
yann@1041
   364
            host_mangle="build_"
yann@1426
   365
            target_mangle=""
yann@1425
   366
            install_build_tools_for="BUILD HOST"
yann@1041
   367
            ;;
yann@1426
   368
        canadian)
yann@1426
   369
            build_mangle="build_"
yann@1426
   370
            host_mangle="host_"
yann@1426
   371
            target_mangle=""
yann@2936
   372
            install_build_tools_for="BUILD HOST"
yann@1426
   373
            ;;
yann@1041
   374
        *)  CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
yann@1041
   375
            ;;
yann@1041
   376
    esac
yann@1033
   377
yann@1041
   378
    # Save the real tuples to generate shell-wrappers to the real tools
yann@1041
   379
    CT_REAL_BUILD="${CT_BUILD}"
yann@1041
   380
    CT_REAL_HOST="${CT_HOST}"
yann@1426
   381
    CT_REAL_TARGET="${CT_TARGET}"
yann@1041
   382
yann@1082
   383
    # Canonicalise CT_BUILD and CT_HOST
yann@1082
   384
    # Not only will it give us full-qualified tuples, but it will also ensure
yann@1082
   385
    # that they are valid tuples (in case of typo with user-provided tuples)
yann@1082
   386
    # That's way better than trying to rewrite config.sub ourselves...
yann@1426
   387
    # CT_TARGET is already made canonical in CT_DoBuildTargetTuple
yann@1089
   388
    CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
yann@1089
   389
    CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
yann@1041
   390
yann@1041
   391
    # Modify BUILD and HOST so that gcc always generate a cross-compiler
yann@1041
   392
    # even if any of the build, host or target machines are the same.
yann@1041
   393
    # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
yann@1041
   394
    #       support canadain build, later...
yann@1041
   395
    CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
yann@1041
   396
    CT_HOST="${CT_HOST/-/-${host_mangle}}"
yann@1426
   397
    CT_TARGET="${CT_TARGET/-/-${target_mangle}}"
yann@1041
   398
yann@1041
   399
    # Now we have mangled our BUILD and HOST tuples, we must fake the new
yann@1041
   400
    # cross-tools for those mangled tuples.
yann@174
   401
    CT_DoLog DEBUG "Making build system tools available"
yann@1425
   402
    for m in ${install_build_tools_for}; do
yann@1041
   403
        r="CT_REAL_${m}"
yann@1041
   404
        v="CT_${m}"
yann@1041
   405
        p="CT_${m}_PREFIX"
yann@1041
   406
        s="CT_${m}_SUFFIX"
yann@1041
   407
        if [ -n "${!p}" ]; then
yann@1041
   408
            t="${!p}"
yann@1041
   409
        else
yann@1041
   410
            t="${!r}-"
yann@1041
   411
        fi
yann@1041
   412
yann@1129
   413
        for tool in ar as dlltool gcc g++ gcj gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
yann@1041
   414
            # First try with prefix + suffix
yann@1041
   415
            # Then try with prefix only
yann@1041
   416
            # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
yann@1041
   417
            # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
yann@1041
   418
            # This is needed, because some tools have a prefix and
yann@1041
   419
            # a suffix (eg. gcc), while others may have only one,
yann@1041
   420
            # or even none (eg. binutils)
yann@1041
   421
            where=$(CT_Which "${t}${tool}${!s}")
yann@1041
   422
            [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
yann@1041
   423
            if [    -z "${where}"                         \
yann@1041
   424
                 -a \(    "${m}" = "BUILD"                \
yann@1041
   425
                       -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
yann@1041
   426
                where=$(CT_Which "${tool}${!s}")
yann@1041
   427
            fi
yann@1041
   428
            if [ -z "${where}"                            \
yann@1041
   429
                 -a \(    "${m}" = "BUILD"                \
yann@1041
   430
                       -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
yann@1041
   431
                where=$(CT_Which "${tool}")
yann@1041
   432
            fi
yann@1041
   433
daniel@3126
   434
            # Not all tools are available for all platforms, but some are required.
yann@1041
   435
            if [ -n "${where}" ]; then
yann@1041
   436
                CT_DoLog DEBUG "  '${!v}-${tool}' -> '${where}'"
titus@2795
   437
                printf "#${BANG}${CT_CONFIG_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_BUILDTOOLS_PREFIX_DIR}/bin/${!v}-${tool}"
yann@2308
   438
                CT_DoExecLog ALL chmod 700 "${CT_BUILDTOOLS_PREFIX_DIR}/bin/${!v}-${tool}"
yann@1041
   439
            else
yann@1041
   440
                case "${tool}" in
yann@1176
   441
                    # We'll at least need some of them...
linux@1927
   442
                    ar|as|gcc|ld|nm|objcopy|objdump|ranlib)
yann@1041
   443
                        CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
yann@1041
   444
                        ;;
yann@1176
   445
                    # Some are conditionnally required
yann@1176
   446
                    # Add them in alphabetical (C locale) ordering
linux@1927
   447
                    g++)
linux@1927
   448
                        # g++ (needed for companion lib), only needed for HOST
linux@1927
   449
                        CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${m}" = "HOST"
linux@1927
   450
                        ;;
yann@1176
   451
                    gcj)
yann@1176
   452
                        CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_CC_LANG_JAVA}" = "y"
yann@1176
   453
                        ;;
linux@2060
   454
                    strip)
linux@2060
   455
                        CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES}" = "y"
linux@2060
   456
                        ;;
yann@1176
   457
                    # If any other is missing, only warn at low level
yann@1041
   458
                    *)
yann@1041
   459
                        # It does not deserve a WARN level.
yann@1041
   460
                        CT_DoLog DEBUG "  Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
yann@1041
   461
                        ;;
yann@1041
   462
                esac
yann@1041
   463
            fi
yann@1041
   464
        done
yann@121
   465
    done
yann@121
   466
yann@2305
   467
    # Some makeinfo versions are a pain in [put your most sensible body part here].
yann@2305
   468
    # Go ahead with those, by creating a wrapper that keeps partial files, and that
yann@2305
   469
    # never fails:
yann@2305
   470
    CT_DoLog DEBUG "  'makeinfo' -> '$(CT_Which makeinfo)'"
titus@2795
   471
    printf "#${BANG}${CT_CONFIG_SHELL}\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue\n" >"${CT_BUILDTOOLS_PREFIX_DIR}/bin/makeinfo"
yann@2308
   472
    CT_DoExecLog ALL chmod 700 "${CT_BUILDTOOLS_PREFIX_DIR}/bin/makeinfo"
yann@2305
   473
yann@1041
   474
    # Carefully add paths in the order we want them:
yann@1041
   475
    #  - first try in ${CT_PREFIX_DIR}/bin
yann@2924
   476
    #  - then try the buildtools dir
yann@1041
   477
    #  - fall back to searching user's PATH
yann@1041
   478
    # Of course, neither cross-native nor canadian can run on BUILD,
yann@1041
   479
    # so don't add those PATHs in this case...
yann@1041
   480
    case "${CT_TOOLCHAIN_TYPE}" in
yann@2924
   481
        cross)  export PATH="${CT_PREFIX_DIR}/bin:${CT_BUILDTOOLS_PREFIX_DIR}/bin:${PATH}";;
yann@2308
   482
        canadian) export PATH="${CT_BUILDTOOLS_PREFIX_DIR}/bin:${PATH}";;
yann@1041
   483
        *)  ;;
yann@1041
   484
    esac
yann@1041
   485
diorcet@3119
   486
    # Help build gcc
diorcet@3119
   487
    # Explicitly optimise, else the lines below will overide the
diorcet@3119
   488
    # package's default optimisation flags
diorcet@3119
   489
    CT_CFLAGS_FOR_BUILD="-O2 -g"
diorcet@3119
   490
    CT_CFLAGS_FOR_BUILD+=" ${CT_EXTRA_CFLAGS_FOR_BUILD}"
diorcet@3119
   491
    CT_LDFLAGS_FOR_BUILD=
diorcet@3119
   492
    CT_LDFLAGS_FOR_BUILD+=" ${CT_EXTRA_LDFLAGS_FOR_BUILD}"
diorcet@3119
   493
    
diorcet@3119
   494
    # Help host gcc
michael@3111
   495
    # Explicitly optimise, else the lines below will overide the
michael@3111
   496
    # package's default optimisation flags
michael@3111
   497
    CT_CFLAGS_FOR_HOST="-O2 -g"
michael@2701
   498
    [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST+=" -pipe"
diorcet@3119
   499
    CT_CFLAGS_FOR_HOST+=" ${CT_EXTRA_CFLAGS_FOR_HOST}"
diorcet@3119
   500
    CT_LDFLAGS_FOR_HOST=
diorcet@3119
   501
    CT_LDFLAGS_FOR_HOST+=" ${CT_EXTRA_LDFLAGS_FOR_HOST}"
daniel@3126
   502
    CT_DoLog DEBUG "CFLAGS for host compiler: '${CT_CFLAGS_FOR_HOST}'"
daniel@3126
   503
    CT_DoLog DEBUG "LDFLAGS for host compiler: '${CT_LDFLAGS_FOR_HOST}'"
yann@121
   504
yann@1033
   505
    # Set the shell to be used by ./configure scripts and by Makefiles (those
yann@1033
   506
    # that support it!).
yann@2705
   507
    export CONFIG_SHELL="${CT_CONFIG_SHELL}"    # for ./configure
yann@2705
   508
    export SHELL="${CT_CONFIG_SHELL}"           # for Makefiles
yann@805
   509
yann@121
   510
    # And help make go faster
yann@2275
   511
    JOBSFLAGS=
yann@2716
   512
    # Override the configured jobs with what's been given on the command line
yann@2716
   513
    [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
michael@2695
   514
    # Use the number of processors+1 when automatically setting the number of
michael@2695
   515
    # parallel jobs.  Fall back to 1 if the host doesn't use GLIBC.
michael@2695
   516
    AUTO_JOBS=$((`getconf _NPROCESSORS_ONLN 2> /dev/null || echo 0` + 1))
yann@2716
   517
    [ ${CT_PARALLEL_JOBS} -eq 0 ] && JOBSFLAGS="${JOBSFLAGS} -j${AUTO_JOBS}"
michael@2695
   518
    [ ${CT_PARALLEL_JOBS} -gt 0 ] && JOBSFLAGS="${JOBSFLAGS} -j${CT_PARALLEL_JOBS}"
yann@2275
   519
    [ ${CT_LOAD} -ne 0 ] && JOBSFLAGS="${JOBSFLAGS} -l${CT_LOAD}"
yann@121
   520
daniel@3126
   521
    # Now that we've set up $PATH and $CT_CFLAGS_FOR_HOST, sanity test that gcc
daniel@3126
   522
    # is runnable so that the user can troubleshoot problems if not.
daniel@3126
   523
    CT_DoStep DEBUG "Checking that we can run gcc -v"
daniel@3126
   524
    CT_DoExecLog DEBUG "${CT_HOST}-gcc" -v
daniel@3126
   525
    CT_EndStep
daniel@3126
   526
daniel@3126
   527
    # Create a simple C program for testing.
daniel@3126
   528
    testc="${CT_BUILD_DIR}/test.c"
daniel@3126
   529
    printf "int main() { return 0; }\n" >"${testc}"
daniel@3126
   530
    gccout="${CT_BUILD_DIR}/.gccout"
daniel@3126
   531
daniel@3126
   532
    CT_DoStep DEBUG "Checking that gcc can compile a trivial program"
daniel@3126
   533
    CT_DoExecLog DEBUG "${CT_HOST}-gcc" ${CT_CFLAGS_FOR_HOST} ${CT_LDFLAGS_FOR_HOST} "${testc}" -o "${gccout}"
daniel@3126
   534
    rm -f "${gccout}"
daniel@3126
   535
    CT_EndStep
daniel@3126
   536
daniel@3126
   537
    if [ "${CT_WANTS_STATIC_LINK}" = "y" ]; then
daniel@3126
   538
        CT_DoStep DEBUG "Checking that gcc can compile a trivial statically linked program (CT_WANTS_STATIC_LINK)"
daniel@3126
   539
        CT_DoLog DEBUG "You may need to ensure that static libraries such as libc.a are installed on your system"
daniel@3126
   540
        CT_DoExecLog DEBUG "${CT_HOST}-gcc" ${CT_CFLAGS_FOR_HOST} ${CT_LDFLAGS_FOR_HOST} "${testc}" -static -o "${gccout}"
daniel@3126
   541
        rm -f "${gccout}"
daniel@3126
   542
        CT_EndStep
daniel@3126
   543
    fi
daniel@3126
   544
daniel@3126
   545
    if [ "${CT_CC_STATIC_LIBSTDCXX}" = "y" ]; then
daniel@3126
   546
        CT_DoStep DEBUG "Checking that gcc can statically link libstdc++ (CT_CC_STATIC_LIBSTDCXX)"
daniel@3126
   547
        CT_DoLog DEBUG "You may need to ensure that libstdc++.a is installed on your system"
daniel@3126
   548
        CT_DoExecLog DEBUG "${CT_HOST}-gcc" ${CT_CFLAGS_FOR_HOST} ${CT_LDFLAGS_FOR_HOST} "${testc}" -static -lstdc++ -o "${gccout}"
daniel@3126
   549
        rm -f "${gccout}"
daniel@3126
   550
        CT_EndStep
daniel@3126
   551
    fi
daniel@3126
   552
    rm -f "${testc}"
daniel@3126
   553
yann@2468
   554
    # We need to save the real .config with kconfig's value,
yann@2468
   555
    # not our mangled .config.2 with arrays.
yann@894
   556
    CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
yann@1423
   557
    CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/bin"
yann@1098
   558
    CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/scripts/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
tvb377@1814
   559
    CT_DoExecLog DEBUG sed -i -e 's,@@grep@@,"'"${grep}"'",;' "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
yann@909
   560
    bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
yann@894
   561
yann@121
   562
    CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
yann@121
   563
    CT_DoLog EXTRA "Building a toolchain for:"
yann@1041
   564
    CT_DoLog EXTRA "  build  = ${CT_REAL_BUILD}"
yann@1041
   565
    CT_DoLog EXTRA "  host   = ${CT_REAL_HOST}"
yann@121
   566
    CT_DoLog EXTRA "  target = ${CT_TARGET}"
yann@1247
   567
    set |grep -E '^CT_.+=' |sort |CT_DoLog DEBUG
yann@1806
   568
    CT_DoLog DEBUG "Other environment:"
yann@1806
   569
    printenv |grep -v -E '^CT_.+=' |CT_DoLog DEBUG
yann@121
   570
    CT_EndStep
yann@63
   571
fi
yann@63
   572
yann@121
   573
if [ -z "${CT_RESTART}" ]; then
yann@2595
   574
    CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
yann@2595
   575
    do_companion_tools_get
yann@2595
   576
    do_kernel_get
Yann@3115
   577
    do_companion_libs_get
yann@2595
   578
    do_binutils_get
yann@2595
   579
    do_cc_get
yann@2595
   580
    do_libc_get
yann@2595
   581
    do_debug_get
yann@2595
   582
    do_test_suite_get
yann@2595
   583
    CT_EndStep
yann@63
   584
yann@121
   585
    if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
yann@121
   586
        if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
yann@1138
   587
            CT_DoForceRmdir "${CT_SRC_DIR}"
yann@1135
   588
            CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
yann@121
   589
        fi
richard@1727
   590
richard@1727
   591
        if [ "${CT_COMP_TOOLS}" = "y" ]; then
richard@1727
   592
          CT_DoStep INFO "Extracting, patching and installing companion tools"
richard@1727
   593
          do_companion_tools_extract
richard@1727
   594
          do_companion_tools
richard@1727
   595
          CT_EndStep
richard@1727
   596
        fi
richard@1727
   597
yann@121
   598
        CT_DoStep INFO "Extracting and patching toolchain components"
yann@121
   599
        do_kernel_extract
Yann@3115
   600
        do_companion_libs_extract
yann@121
   601
        do_binutils_extract
yann@331
   602
        do_cc_extract
yann@121
   603
        do_libc_extract
yann@121
   604
        do_debug_extract
mgl@1965
   605
        do_test_suite_extract
yann@121
   606
        CT_EndStep
yann@121
   607
    fi
yann@121
   608
fi
yann@85
   609
yann@121
   610
# Now for the job by itself. Go have a coffee!
yann@121
   611
if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
yann@121
   612
    # Because of CT_RESTART, this becomes quite complex
yann@143
   613
    do_stop=0
yann@143
   614
    prev_step=
yann@121
   615
    [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
yann@466
   616
    # Aha! CT_STEPS comes from steps.mk!
yann@461
   617
    for step in ${CT_STEPS}; do
yann@121
   618
        if [ ${do_it} -eq 0 ]; then
yann@121
   619
            if [ "${CT_RESTART}" = "${step}" ]; then
yann@121
   620
                CT_DoLoadState "${step}"
yann@121
   621
                do_it=1
yann@143
   622
                do_stop=0
yann@121
   623
            fi
yann@121
   624
        else
yann@121
   625
            CT_DoSaveState ${step}
yann@143
   626
            if [ ${do_stop} -eq 1 ]; then
yann@523
   627
                CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
yann@143
   628
                exit 0
yann@143
   629
            fi
yann@85
   630
        fi
yann@121
   631
        if [ ${do_it} -eq 1 ]; then
yann@2707
   632
            ( do_${step} )
yann@2964
   633
            # POSIX 1003.1-2008 does not say if "set -e" should catch a
yann@2964
   634
            # sub-shell ending with !0. bash-3 does not, while bash-4 does,
yann@2964
   635
            # so the following line is for bash-3; bash-4 would choke above.
yann@2973
   636
            [ $? -eq 0 ]
yann@135
   637
            if [ "${CT_STOP}" = "${step}" ]; then
yann@143
   638
                do_stop=1
yann@135
   639
            fi
yann@725
   640
            if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
yann@523
   641
                CT_DoPause "Step '${step}' finished"
yann@121
   642
            fi
yann@121
   643
        fi
yann@143
   644
        prev_step="${step}"
yann@121
   645
    done
yann@63
   646
fi
yann@1
   647
yann@96
   648
CT_DoEnd INFO
yann@96
   649
yann@1135
   650
# From now-on, it can become impossible to log any time, because
yann@1135
   651
# either we're compressing the log file, or it can become RO any
yann@1135
   652
# moment... Consign all ouptut to oblivion...
yann@1135
   653
CT_DoLog INFO "Finishing installation (may take a few seconds)..."
yann@1135
   654
exec >/dev/null 2>&1
yann@2550
   655
rm -f ${CT_PREFIX_DIR}/build.log.bz2
yann@2339
   656
if [ "${CT_LOG_TO_FILE}" = "y" ]; then
yann@2339
   657
    cp "${tmp_log_file}" "${CT_PREFIX_DIR}/build.log"
yann@2339
   658
    if [ "${CT_LOG_FILE_COMPRESS}" = y ]; then
yann@2339
   659
        bzip2 -9 "${CT_PREFIX_DIR}/build.log"
yann@2339
   660
    fi
yann@2339
   661
fi
yann@1135
   662
[ "${CT_INSTALL_DIR_RO}" = "y"  ] && chmod -R a-w "${CT_INSTALL_DIR}"
yann@1966
   663
[ "${CT_TEST_SUITE}" = "y" ] && chmod -R u+w "${CT_TEST_SUITE_DIR}"
yann@1
   664
yann@1
   665
trap - EXIT