scripts/crosstool-NG.sh.in
author "Yann E. MORIN" <yann.morin.1998@free.fr>
Thu Nov 22 19:43:26 2012 +0100 (2012-11-22)
branch1.17
changeset 3130 8db540910974
parent 3083 3a7b2eee9dcd
permissions -rw-r--r--
scripts/functions: fix debug-shell

Properly catch resuming the build when continuing past the
failed command.

The 'case ;;&' construct is a bash4ism. Get rid of it.

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