scripts/crosstool.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Thu Nov 13 18:22:23 2008 +0000 (2008-11-13)
changeset 1041 2573519c00d6
parent 1038 33f695f7773a
child 1062 a435f445d477
permissions -rwxr-xr-x
Merge #1195, #1196 and #1203 from /devel/YEM-build_host_target_cleanup:
- Get rid of CT_CC_NATIVE
- Get rid of CT_CANADIAN_OPT
- Sanitise CT_BUILD vs. CT_HOST

/trunk/scripts/build/tools/200-sstrip.sh | 4 2 2 0
/trunk/scripts/build/binutils.sh | 1 0 1 0 -
/trunk/scripts/build/cc/gcc.sh | 11 6 5 0 +-
/trunk/scripts/build/debug/200-duma.sh | 3 1 2 0 -
/trunk/scripts/build/libc/glibc.sh | 10 5 5 0 +-
/trunk/scripts/build/libc/eglibc.sh | 8 4 4 0 +-
/trunk/scripts/crosstool.sh | 168 113 55 0 ++++++++++++++++++++++++++------------
/trunk/config/toolchain.in | 160 137 23 0 +++++++++++++++++++++++++++++++-----
8 files changed, 268 insertions(+), 97 deletions(-)
yann@1
     1
#!/bin/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@523
    23
CT_STAR_DATE=$(CT_DoDate +%s%N)
yann@523
    24
CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
yann@1
    25
yann@1
    26
# Parse the configuration file
yann@96
    27
# It has some info about the logging facility, so include it early
yann@965
    28
. .config
yann@1
    29
yann@379
    30
# Yes! We can do full logging from now on!
yann@379
    31
CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
yann@379
    32
yann@96
    33
# renice oursleves
yann@762
    34
CT_DoExecLog DEBUG renice ${CT_NICE} $$
yann@1
    35
yann@894
    36
CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
yann@965
    37
CT_DoExecLog DEBUG egrep '^(# |)CT_' .config
yann@96
    38
CT_EndStep
yann@63
    39
yann@1
    40
# Some sanity checks in the environment and needed tools
yann@1
    41
CT_DoLog INFO "Checking environment sanity"
yann@1
    42
yann@290
    43
CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
yann@290
    44
unset MAKEFLAGS
yann@290
    45
export MAKEFLAGS
yann@290
    46
yann@1
    47
# Other environment sanity checks
yann@1
    48
CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
yann@1
    49
CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
yann@1
    50
CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
yann@1
    51
CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
yann@965
    52
export GREP_OPTIONS=
yann@1
    53
yann@1
    54
CT_DoLog INFO "Building environment variables"
yann@1
    55
yann@965
    56
# Include sub-scripts instead of calling them: that way, we do not have to
yann@965
    57
# export any variable, nor re-parse the configuration and functions files.
yann@903
    58
. "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
yann@965
    59
. "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
yann@965
    60
. "${CT_LIB_DIR}/scripts/build/gmp.sh"
yann@965
    61
. "${CT_LIB_DIR}/scripts/build/mpfr.sh"
yann@965
    62
. "${CT_LIB_DIR}/scripts/build/binutils.sh"
yann@965
    63
. "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
yann@965
    64
. "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
yann@965
    65
. "${CT_LIB_DIR}/scripts/build/tools.sh"
yann@965
    66
. "${CT_LIB_DIR}/scripts/build/debug.sh"
yann@380
    67
yann@335
    68
# Target tuple: CT_TARGET needs a little love:
yann@335
    69
CT_DoBuildTargetTuple
yann@1
    70
yann@96
    71
# Kludge: If any of the configured options needs CT_TARGET,
yann@96
    72
# then rescan the options file now:
yann@96
    73
. "${CT_TOP_DIR}/.config"
yann@96
    74
yann@397
    75
# Second kludge: merge user-supplied target CFLAGS with architecture-provided
yann@531
    76
# target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
yann@531
    77
# Put user-supplied flags at the end, so that they take precedence.
yann@397
    78
CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
yann@531
    79
CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
yann@767
    80
CT_CC_CORE_EXTRA_CONFIG="${CT_ARCH_CC_CORE_EXTRA_CONFIG} ${CT_CC_CORE_EXTRA_CONFIG}"
yann@767
    81
CT_CC_EXTRA_CONFIG="${CT_ARCH_CC_EXTRA_CONFIG} ${CT_CC_EXTRA_CONFIG}"
yann@397
    82
yann@1
    83
# Now, build up the variables from the user-configured options.
yann@1
    84
CT_KERNEL_FILE="${CT_KERNEL}-${CT_KERNEL_VERSION}"
yann@1
    85
CT_BINUTILS_FILE="binutils-${CT_BINUTILS_VERSION}"
yann@466
    86
CT_GMP_FILE="gmp-${CT_GMP_VERSION}"
yann@466
    87
CT_MPFR_FILE="mpfr-${CT_MPFR_VERSION}"
yann@1
    88
CT_CC_FILE="${CT_CC}-${CT_CC_VERSION}"
yann@1
    89
CT_LIBC_FILE="${CT_LIBC}-${CT_LIBC_VERSION}"
yann@1
    90
yann@85
    91
# Where will we work?
yann@610
    92
: "${CT_WORK_DIR:=${CT_TOP_DIR}/targets}"
yann@610
    93
CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
yann@610
    94
CT_SRC_DIR="${CT_WORK_DIR}/src"
yann@610
    95
CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
yann@96
    96
CT_DEBUG_INSTALL_DIR="${CT_INSTALL_DIR}/${CT_TARGET}/debug-root"
yann@121
    97
# Note: we'll always install the core compiler in its own directory, so as to
yann@331
    98
# not mix the two builds: core and final.
yann@136
    99
CT_CC_CORE_STATIC_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-static"
yann@136
   100
CT_CC_CORE_SHARED_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-shared"
yann@610
   101
CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
yann@85
   102
yann@143
   103
# We must ensure that we can restart if asked for!
yann@143
   104
if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}"  ]; then
yann@143
   105
    CT_DoLog ERROR "You asked to restart a non-restartable build"
yann@143
   106
    CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
yann@153
   107
    CT_DoLog ERROR "in the config options for the previous build, or the state"
yann@425
   108
    CT_DoLog ERROR "directory for the previous build was deleted."
yann@143
   109
    CT_Abort "I will stop here to avoid any carnage"
yann@143
   110
fi
yann@143
   111
yann@754
   112
if [ -n "${CT_LOCAL_TARBALLS_DIR}" ]; then
yann@754
   113
    # Make absolute path, it so much easier!
yann@754
   114
    CT_LOCAL_TARBALLS_DIR=$(CT_MakeAbsolutePath "${CT_LOCAL_TARBALLS_DIR}")
yann@754
   115
fi
yann@85
   116
yann@403
   117
# If the local tarball directory does not exist, say so, and don't try to save there!
yann@403
   118
if [ ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
yann@523
   119
    CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist. Will not save downloaded tarballs to local storage."
yann@523
   120
    CT_SAVE_TARBALLS=
yann@403
   121
fi
yann@403
   122
yann@1
   123
# Some more sanity checks now that we have all paths set up
yann@403
   124
case "${CT_LOCAL_TARBALLS_DIR},${CT_TARBALLS_DIR},${CT_SRC_DIR},${CT_BUILD_DIR},${CT_PREFIX_DIR},${CT_INSTALL_DIR}" in
yann@1
   125
    *" "*) CT_Abort "Don't use spaces in paths, it breaks things.";;
yann@1
   126
esac
yann@1
   127
yann@85
   128
# Check now if we can write to the destination directory:
yann@85
   129
if [ -d "${CT_INSTALL_DIR}" ]; then
yann@523
   130
    CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
yann@85
   131
fi
yann@85
   132
yann@96
   133
# Good, now grab a bit of informations on the system we're being run on,
yann@96
   134
# just in case something goes awok, and it's not our fault:
yann@523
   135
CT_SYS_USER=$(id -un)
yann@523
   136
CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
yann@96
   137
# Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
yann@523
   138
CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
yann@523
   139
CT_SYS_KERNEL=$(uname -s)
yann@523
   140
CT_SYS_REVISION=$(uname -r)
yann@96
   141
# MacOS X lacks '-o' :
yann@523
   142
CT_SYS_OS=$(uname -o || echo "Unknown (maybe MacOS-X)")
yann@523
   143
CT_SYS_MACHINE=$(uname -m)
yann@523
   144
CT_SYS_PROCESSOR=$(uname -p)
yann@523
   145
CT_SYS_GCC=$(gcc -dumpversion)
yann@523
   146
CT_SYS_TARGET=$(CT_DoConfigGuess)
yann@96
   147
CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
yann@96
   148
yann@96
   149
CT_DoLog EXTRA "Preparing working directories"
yann@96
   150
yann@121
   151
# Ah! The build directory shall be eradicated, even if we restart!
yann@85
   152
if [ -d "${CT_BUILD_DIR}" ]; then
yann@85
   153
    mv "${CT_BUILD_DIR}" "${CT_BUILD_DIR}.$$"
yann@96
   154
    chmod -R u+w "${CT_BUILD_DIR}.$$"
yann@320
   155
    setsid nohup rm -rf "${CT_BUILD_DIR}.$$" >/dev/null 2>&1 &
yann@85
   156
fi
yann@121
   157
yann@121
   158
# Don't eradicate directories if we need to restart
yann@121
   159
if [ -z "${CT_RESTART}" ]; then
yann@121
   160
    # Get rid of pre-existing installed toolchain and previous build directories.
yann@121
   161
    # We need to do that _before_ we can safely log, because the log file will
yann@121
   162
    # most probably be in the toolchain directory.
yann@121
   163
    if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
yann@121
   164
        mv "${CT_TARBALLS_DIR}" "${CT_TARBALLS_DIR}.$$"
yann@121
   165
        chmod -R u+w "${CT_TARBALLS_DIR}.$$"
yann@320
   166
        setsid nohup rm -rf "${CT_TARBALLS_DIR}.$$" >/dev/null 2>&1 &
yann@121
   167
    fi
yann@121
   168
    if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
yann@121
   169
        mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
yann@121
   170
        chmod -R u+w "${CT_SRC_DIR}.$$"
yann@320
   171
        setsid nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1 &
yann@121
   172
    fi
yann@121
   173
    if [ -d "${CT_INSTALL_DIR}" ]; then
yann@121
   174
        mv "${CT_INSTALL_DIR}" "${CT_INSTALL_DIR}.$$"
yann@121
   175
        chmod -R u+w "${CT_INSTALL_DIR}.$$"
yann@320
   176
        setsid nohup rm -rf "${CT_INSTALL_DIR}.$$" >/dev/null 2>&1 &
yann@121
   177
    fi
yann@121
   178
    if [ -d "${CT_DEBUG_INSTALL_DIR}" ]; then
yann@121
   179
        mv "${CT_DEBUG_INSTALL_DIR}" "${CT_DEBUG_INSTALL_DIR}.$$"
yann@121
   180
        chmod -R u+w "${CT_DEBUG_INSTALL_DIR}.$$"
yann@320
   181
        setsid nohup rm -rf "${CT_DEBUG_INSTALL_DIR}.$$" >/dev/null 2>&1 &
yann@121
   182
    fi
yann@121
   183
    # In case we start anew, get rid of the previously saved state directory
yann@121
   184
    if [ -d "${CT_STATE_DIR}" ]; then
yann@121
   185
        mv "${CT_STATE_DIR}" "${CT_STATE_DIR}.$$"
yann@121
   186
        chmod -R u+w "${CT_STATE_DIR}.$$"
yann@320
   187
        setsid nohup rm -rf "${CT_STATE_DIR}.$$" >/dev/null 2>&1 &
yann@121
   188
    fi
yann@96
   189
fi
yann@85
   190
yann@121
   191
# Create the directories we'll use, even if restarting: it does no harm to
yann@121
   192
# create already existent directories, and CT_BUILD_DIR needs to be created
yann@121
   193
# anyway
yann@85
   194
mkdir -p "${CT_TARBALLS_DIR}"
yann@85
   195
mkdir -p "${CT_SRC_DIR}"
yann@85
   196
mkdir -p "${CT_BUILD_DIR}"
yann@85
   197
mkdir -p "${CT_INSTALL_DIR}"
yann@121
   198
mkdir -p "${CT_PREFIX_DIR}"
yann@96
   199
mkdir -p "${CT_DEBUG_INSTALL_DIR}"
yann@136
   200
mkdir -p "${CT_CC_CORE_STATIC_PREFIX_DIR}"
yann@136
   201
mkdir -p "${CT_CC_CORE_SHARED_PREFIX_DIR}"
yann@121
   202
mkdir -p "${CT_STATE_DIR}"
yann@121
   203
yann@121
   204
# Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
yann@425
   205
# the previous build was successful. To be able to move the logfile there,
yann@121
   206
# switch them back to read/write
yann@121
   207
chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
yann@85
   208
yann@63
   209
# Redirect log to the actual log file now we can
yann@63
   210
# It's quite understandable that the log file will be installed in the install
yann@63
   211
# directory, so we must first ensure it exists and is writeable (above) before
yann@63
   212
# we can log there
yann@112
   213
exec >/dev/null
yann@174
   214
case "${CT_LOG_TO_FILE}" in
yann@174
   215
    y)  CT_LOG_FILE="${CT_PREFIX_DIR}/build.log"
yann@174
   216
        cat "${tmp_log_file}" >>"${CT_LOG_FILE}"
yann@174
   217
        rm -f "${tmp_log_file}"
yann@174
   218
        exec >>"${CT_LOG_FILE}"
yann@174
   219
        ;;
yann@174
   220
    *)  rm -f "${tmp_log_file}"
yann@174
   221
        ;;
yann@63
   222
esac
yann@63
   223
yann@397
   224
# Setting up the rest of the environment only if not restarting
yann@121
   225
if [ -z "${CT_RESTART}" ]; then
yann@1041
   226
    # What's our shell?
yann@1041
   227
    # Will be plain /bin/sh on most systems, except if we have /bin/ash and we
yann@1041
   228
    # _explictly_ required using it
yann@1041
   229
    CT_SHELL="/bin/sh"
yann@1041
   230
    [ "${CT_CONFIG_SHELL_ASH}" = "y" -a -x "/bin/ash" ] && CT_SHELL="/bin/ash"
yann@63
   231
yann@121
   232
    # Arrange paths depending on wether we use sys-root or not.
yann@121
   233
    if [ "${CT_USE_SYSROOT}" = "y" ]; then
yann@121
   234
        CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/sys-root"
yann@121
   235
        CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
yann@121
   236
        BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   237
        CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   238
        CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   239
        LIBC_SYSROOT_ARG=""
yann@121
   240
        # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
yann@121
   241
        # confused when $sysroot/usr/include is not present.
yann@121
   242
        # Note: --prefix=/usr is magic!
yann@121
   243
        # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
yann@121
   244
    else
yann@121
   245
        # plain old way. All libraries in prefix/target/lib
yann@121
   246
        CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
yann@121
   247
        CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
yann@121
   248
        # hack!  Always use --with-sysroot for binutils.
yann@121
   249
        # binutils 2.14 and later obey it, older binutils ignore it.
yann@121
   250
        # Lets you build a working 32->64 bit cross gcc
yann@121
   251
        BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
yann@121
   252
        # Use --with-headers, else final gcc will define disable_glibc while
yann@121
   253
        # building libgcc, and you'll have no profiling
yann@121
   254
        CC_CORE_SYSROOT_ARG="--without-headers"
yann@121
   255
        CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
yann@121
   256
        LIBC_SYSROOT_ARG="prefix="
yann@121
   257
    fi
yann@121
   258
yann@121
   259
    # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
yann@121
   260
    # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail with
yann@121
   261
    #  "ld: cannot open crti.o: No such file or directory"
yann@121
   262
    mkdir -p "${CT_SYSROOT_DIR}/lib"
yann@121
   263
    mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
yann@121
   264
yann@740
   265
    # Prevent gcc from installing its libraries outside of the sys-root
yann@740
   266
    ln -sf "sys-root/lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib"
yann@740
   267
yann@740
   268
    # Now, in case we're 64 bits, just have lib64/ be a symlink to lib/
yann@740
   269
    # so as to have all libraries in the same directory (we can do that
yann@740
   270
    # because we are *not* multilib).
yann@1038
   271
    if [ "${CT_ARCH_64}" = "y" ]; then
yann@1038
   272
        ln -sf "lib" "${CT_SYSROOT_DIR}/lib64"
yann@1038
   273
        ln -sf "lib" "${CT_SYSROOT_DIR}/usr/lib64"
yann@1038
   274
        ln -sf "sys-root/lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib64"
yann@1038
   275
    fi
yann@740
   276
yann@1041
   277
    # Determine build system if not set by the user
yann@1041
   278
    CT_Test "You did not specify the build system. That's OK, I can guess..." -z "${CT_BUILD}"
yann@1041
   279
    case "${CT_BUILD}" in
yann@1041
   280
        "") CT_BUILD=$(gcc -dumpmachine);;
yann@1041
   281
        *)  CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}");;
yann@121
   282
    esac
yann@121
   283
yann@1041
   284
    # Prepare mangling patterns to later modifyu BUILD and HOST (see below)
yann@1041
   285
    case "${CT_TOOLCHAIN_TYPE}" in
yann@1041
   286
        cross)
yann@1041
   287
            CT_HOST="${CT_BUILD}"
yann@1041
   288
            build_mangle="build_"
yann@1041
   289
            host_mangle="build_"
yann@1041
   290
            ;;
yann@1041
   291
        *)  CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
yann@1041
   292
            ;;
yann@1041
   293
    esac
yann@1033
   294
yann@1041
   295
    # Save the real tuples to generate shell-wrappers to the real tools
yann@1041
   296
    CT_REAL_BUILD="${CT_BUILD}"
yann@1041
   297
    CT_REAL_HOST="${CT_HOST}"
yann@1041
   298
yann@1041
   299
    # Make BUILD and HOST full-fledge four-part tuples (gcc -dumpmachine
yann@1041
   300
    # might be only three-part tuple, and I don't know wether config.guess
yann@1041
   301
    # can return 3-part tuples...)
yann@1041
   302
    case "${CT_BUILD}" in
yann@1041
   303
        *-*-*-*-*)  CT_Abort "Unexpected 5-part (or more) build tuple: '${CT_BUILD}'";;
yann@1041
   304
        *-*-*-*)    ;;
yann@1041
   305
        *-*-*)      CT_BUILD="${CT_BUILD/-/-unknown-}";;
yann@1041
   306
        *)          CT_Abort "Unepxected 1- or 2-part build tuple: '${CT_BUILD}'";;
yann@1041
   307
    esac
yann@1041
   308
    case "${CT_HOST}" in
yann@1041
   309
        *-*-*-*-*)  CT_Abort "Unexpected 5-part (or more) host tuple: '${CT_HOST}'";;
yann@1041
   310
        *-*-*-*)    ;;
yann@1041
   311
        *-*-*)      CT_HOST="${CT_HOST/-/-unknown-}";;
yann@1041
   312
        *)          CT_Abort "Unepxected 1- or 2-part host tuple: '${CT_HOST}'";;
yann@1041
   313
    esac
yann@1041
   314
yann@1041
   315
    # Modify BUILD and HOST so that gcc always generate a cross-compiler
yann@1041
   316
    # even if any of the build, host or target machines are the same.
yann@1041
   317
    # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
yann@1041
   318
    #       support canadain build, later...
yann@1041
   319
    CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
yann@1041
   320
    CT_HOST="${CT_HOST/-/-${host_mangle}}"
yann@1041
   321
yann@1041
   322
    # Now we have mangled our BUILD and HOST tuples, we must fake the new
yann@1041
   323
    # cross-tools for those mangled tuples.
yann@1033
   324
    BANG='!'
yann@174
   325
    CT_DoLog DEBUG "Making build system tools available"
yann@121
   326
    mkdir -p "${CT_PREFIX_DIR}/bin"
yann@1041
   327
    for m in BUILD HOST; do
yann@1041
   328
        r="CT_REAL_${m}"
yann@1041
   329
        v="CT_${m}"
yann@1041
   330
        p="CT_${m}_PREFIX"
yann@1041
   331
        s="CT_${m}_SUFFIX"
yann@1041
   332
        if [ -n "${!p}" ]; then
yann@1041
   333
            t="${!p}"
yann@1041
   334
        else
yann@1041
   335
            t="${!r}-"
yann@1041
   336
        fi
yann@1041
   337
yann@1041
   338
        for tool in ar as dlltool gcc g++ gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
yann@1041
   339
            # First try with prefix + suffix
yann@1041
   340
            # Then try with prefix only
yann@1041
   341
            # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
yann@1041
   342
            # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
yann@1041
   343
            # This is needed, because some tools have a prefix and
yann@1041
   344
            # a suffix (eg. gcc), while others may have only one,
yann@1041
   345
            # or even none (eg. binutils)
yann@1041
   346
            where=$(CT_Which "${t}${tool}${!s}")
yann@1041
   347
            [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
yann@1041
   348
            if [    -z "${where}"                         \
yann@1041
   349
                 -a \(    "${m}" = "BUILD"                \
yann@1041
   350
                       -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
yann@1041
   351
                where=$(CT_Which "${tool}${!s}")
yann@1041
   352
            fi
yann@1041
   353
            if [ -z "${where}"                            \
yann@1041
   354
                 -a \(    "${m}" = "BUILD"                \
yann@1041
   355
                       -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
yann@1041
   356
                where=$(CT_Which "${tool}")
yann@1041
   357
            fi
yann@1041
   358
yann@1041
   359
            # Not all tools are available for all platforms, but some are really,
yann@1041
   360
            # bally needed
yann@1041
   361
            if [ -n "${where}" ]; then
yann@1041
   362
                CT_DoLog DEBUG "  '${!v}-${tool}' -> '${where}'"
yann@1041
   363
                printf "#${BANG}${CT_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_PREFIX_DIR}/bin/${!v}-${tool}"
yann@1041
   364
                chmod 700 "${CT_PREFIX_DIR}/bin/${!v}-${tool}"
yann@1041
   365
            else
yann@1041
   366
                # We'll at least need some of them...
yann@1041
   367
                case "${tool}" in
yann@1041
   368
                    ar|as|gcc|ld|nm|objcopy|objdump|ranlib)
yann@1041
   369
                        CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
yann@1041
   370
                        ;;
yann@1041
   371
                    *)
yann@1041
   372
                        # It does not deserve a WARN level.
yann@1041
   373
                        CT_DoLog DEBUG "  Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
yann@1041
   374
                        ;;
yann@1041
   375
                esac
yann@1041
   376
            fi
yann@1041
   377
        done
yann@121
   378
    done
yann@121
   379
yann@1041
   380
    # Carefully add paths in the order we want them:
yann@1041
   381
    #  - first try in ${CT_PREFIX_DIR}/bin
yann@1041
   382
    #  - then try in ${CT_CC_CORE_SHARED_PREFIX_DIR}/bin
yann@1041
   383
    #  - then try in ${CT_CC_CORE_STATIC_PREFIX_DIR}/bin
yann@1041
   384
    #  - fall back to searching user's PATH
yann@1041
   385
    # Of course, neither cross-native nor canadian can run on BUILD,
yann@1041
   386
    # so don't add those PATHs in this case...
yann@1041
   387
    case "${CT_TOOLCHAIN_TYPE}" in
yann@1041
   388
        cross)  export PATH="${CT_PREFIX_DIR}/bin:${CT_CC_CORE_SHARED_PREFIX_DIR}/bin:${CT_CC_CORE_STATIC_PREFIX_DIR}/bin:${PATH}";;
yann@1041
   389
        *)  ;;
yann@1041
   390
    esac
yann@1041
   391
yann@564
   392
    # Some makeinfo versions are a pain in [put your most sensible body part here].
yann@564
   393
    # Go ahead with those, by creating a wrapper that keeps partial files, and that
yann@564
   394
    # never fails:
yann@564
   395
    echo -e "#!/bin/sh\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue" >"${CT_PREFIX_DIR}/bin/makeinfo"
yann@564
   396
    chmod 700 "${CT_PREFIX_DIR}/bin/makeinfo"
yann@564
   397
yann@121
   398
    # Help gcc
yann@121
   399
    CT_CFLAGS_FOR_HOST=
yann@121
   400
    [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
yann@121
   401
yann@333
   402
    # Override the configured jobs with what's been given on the command line
yann@333
   403
    [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
yann@333
   404
yann@1033
   405
    # Set the shell to be used by ./configure scripts and by Makefiles (those
yann@1033
   406
    # that support it!).
yann@1033
   407
    export CONFIG_SHELL="${CT_SHELL}"
yann@805
   408
yann@121
   409
    # And help make go faster
yann@121
   410
    PARALLELMFLAGS=
yann@121
   411
    [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
yann@121
   412
    [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
yann@568
   413
    export PARALLELMFLAGS
yann@121
   414
yann@894
   415
    CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
yann@909
   416
    CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/tools/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
yann@909
   417
    bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
yann@894
   418
yann@121
   419
    CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
yann@121
   420
    CT_DoLog EXTRA "Building a toolchain for:"
yann@1041
   421
    CT_DoLog EXTRA "  build  = ${CT_REAL_BUILD}"
yann@1041
   422
    CT_DoLog EXTRA "  host   = ${CT_REAL_HOST}"
yann@121
   423
    CT_DoLog EXTRA "  target = ${CT_TARGET}"
yann@121
   424
    set |egrep '^CT_.+=' |sort |CT_DoLog DEBUG
yann@121
   425
    CT_EndStep
yann@63
   426
fi
yann@63
   427
yann@121
   428
if [ -z "${CT_RESTART}" ]; then
yann@121
   429
    CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
yann@121
   430
    do_kernel_get
yann@466
   431
    do_gmp_get
yann@466
   432
    do_mpfr_get
yann@121
   433
    do_binutils_get
yann@331
   434
    do_cc_get
yann@121
   435
    do_libc_get
yann@148
   436
    do_tools_get
yann@121
   437
    do_debug_get
yann@63
   438
    CT_EndStep
yann@63
   439
yann@121
   440
    if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
yann@121
   441
        if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
yann@507
   442
            mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.force.$$"
yann@507
   443
            setsid nohup rm -rf "${CT_SRC_DIR}.force.$$" >/dev/null 2>&1
yann@507
   444
            mkdir -p "${CT_SRC_DIR}"
yann@121
   445
        fi
yann@121
   446
        CT_DoStep INFO "Extracting and patching toolchain components"
yann@121
   447
        do_kernel_extract
yann@466
   448
        do_gmp_extract
yann@466
   449
        do_mpfr_extract
yann@121
   450
        do_binutils_extract
yann@331
   451
        do_cc_extract
yann@121
   452
        do_libc_extract
yann@148
   453
        do_tools_extract
yann@121
   454
        do_debug_extract
yann@121
   455
        CT_EndStep
yann@121
   456
    fi
yann@121
   457
fi
yann@85
   458
yann@121
   459
# Now for the job by itself. Go have a coffee!
yann@121
   460
if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
yann@121
   461
    # Because of CT_RESTART, this becomes quite complex
yann@143
   462
    do_stop=0
yann@143
   463
    prev_step=
yann@121
   464
    [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
yann@466
   465
    # Aha! CT_STEPS comes from steps.mk!
yann@461
   466
    for step in ${CT_STEPS}; do
yann@121
   467
        if [ ${do_it} -eq 0 ]; then
yann@121
   468
            if [ "${CT_RESTART}" = "${step}" ]; then
yann@121
   469
                CT_DoLoadState "${step}"
yann@121
   470
                do_it=1
yann@143
   471
                do_stop=0
yann@121
   472
            fi
yann@121
   473
        else
yann@121
   474
            CT_DoSaveState ${step}
yann@143
   475
            if [ ${do_stop} -eq 1 ]; then
yann@523
   476
                CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
yann@143
   477
                exit 0
yann@143
   478
            fi
yann@85
   479
        fi
yann@121
   480
        if [ ${do_it} -eq 1 ]; then
yann@121
   481
            do_${step}
yann@135
   482
            if [ "${CT_STOP}" = "${step}" ]; then
yann@143
   483
                do_stop=1
yann@135
   484
            fi
yann@725
   485
            if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
yann@523
   486
                CT_DoPause "Step '${step}' finished"
yann@121
   487
            fi
yann@121
   488
        fi
yann@143
   489
        prev_step="${step}"
yann@121
   490
    done
yann@85
   491
yann@762
   492
    CT_DoLog INFO "================================================================="
yann@762
   493
yann@274
   494
    CT_DoLog DEBUG "Removing access to the build system tools"
yann@419
   495
    find "${CT_PREFIX_DIR}/bin" -name "${CT_BUILD}-"'*' -exec rm -fv {} \; |CT_DoLog DEBUG
yann@419
   496
    find "${CT_PREFIX_DIR}/bin" -name "${CT_HOST}-"'*' -exec rm -fv {} \; |CT_DoLog DEBUG
yann@564
   497
    rm -fv "${CT_PREFIX_DIR}/bin/makeinfo" |CT_DoLog DEBUG
yann@274
   498
yann@850
   499
    if [ "${CT_BARE_METAL}" != "y" ]; then
yann@850
   500
        CT_DoLog EXTRA "Installing the populate helper"
yann@850
   501
        sed -r -e 's|@@CT_TARGET@@|'"${CT_TARGET}"'|g;' \
yann@850
   502
            "${CT_LIB_DIR}/tools/populate.in"           \
yann@850
   503
            >"${CT_PREFIX_DIR}/bin/${CT_TARGET}-populate"
yann@850
   504
        chmod 755 "${CT_PREFIX_DIR}/bin/${CT_TARGET}-populate"
yann@850
   505
    fi
yann@217
   506
yann@121
   507
    # Create the aliases to the target tools
yann@762
   508
    CT_DoLog EXTRA "Creating toolchain aliases"
yann@321
   509
    CT_Pushd "${CT_PREFIX_DIR}/bin"
yann@321
   510
    for t in "${CT_TARGET}-"*; do
yann@321
   511
        if [ -n "${CT_TARGET_ALIAS}" ]; then
yann@523
   512
            _t=$(echo "$t" |sed -r -e 's/^'"${CT_TARGET}"'-/'"${CT_TARGET_ALIAS}"'-/;')
yann@755
   513
            ln -sv "${t}" "${_t}" 2>&1
yann@321
   514
        fi
yann@321
   515
        if [ -n "${CT_TARGET_ALIAS_SED_EXPR}" ]; then
yann@523
   516
            _t=$(echo "$t" |sed -r -e "${CT_TARGET_ALIAS_SED_EXPR}")
yann@755
   517
            ln -sv "${t}" "${_t}" 2>&1
yann@321
   518
        fi
yann@755
   519
    done |CT_DoLog ALL
yann@321
   520
    CT_Popd
yann@121
   521
yann@121
   522
    # Remove the generated documentation files
yann@121
   523
    if [ "${CT_REMOVE_DOCS}" = "y" ]; then
yann@121
   524
    	CT_DoLog INFO "Removing installed documentation"
yann@121
   525
        rm -rf "${CT_PREFIX_DIR}/"{,usr/}{man,info}
yann@121
   526
        rm -rf "${CT_SYSROOT_DIR}/"{,usr/}{man,info}
yann@121
   527
        rm -rf "${CT_DEBUG_INSTALL_DIR}/"{,usr/}{man,info}
yann@63
   528
    fi
yann@63
   529
fi
yann@1
   530
yann@96
   531
CT_DoEnd INFO
yann@96
   532
yann@174
   533
if [ "${CT_LOG_FILE_COMPRESS}" = y ]; then
yann@174
   534
    CT_DoLog EXTRA "Compressing log file"
yann@174
   535
    exec >/dev/null
yann@174
   536
    bzip2 -9 "${CT_LOG_FILE}"
yann@174
   537
fi
yann@174
   538
yann@174
   539
if [ "${CT_INSTALL_DIR_RO}" = "y" ]; then
yann@174
   540
    # OK, now we're done, set the toolchain read-only
yann@174
   541
    # Don't log, the log file may become read-only any moment...
yann@174
   542
    chmod -R a-w "${CT_INSTALL_DIR}" >/dev/null 2>&1
yann@174
   543
fi
yann@1
   544
yann@1
   545
trap - EXIT