scripts/crosstool-NG.sh.in
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun May 24 22:04:14 2009 +0000 (2009-05-24)
branchgcc-4.4
changeset 1380 945dc995daa7
parent 1345 27fec561af53
child 1384 b23f3c2e0c73
permissions -rw-r--r--
/devel/gcc-4.4:
- add support for building CLooG

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