scripts/crosstool.sh
author "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Sun Sep 14 16:21:07 2008 +0000 (2008-09-14)
changeset 850 ef8549b58b6f
parent 847 af75fc1fe0fc
child 894 c444ce4b51b9
permissions -rwxr-xr-x
Introduce a new EXPERIMENTAL feature: BARE_METAL.
This should ultimately llow to build bare-metal compilers, for targets that have no kernel and no C library.
Move the C library build script to their own sub-directory; introduce an empty build script for bare-metal.
Move the compiler build script to its own sub-directory.
Move the kernel build script to its own sub-directory; introduce an empty build script for bare-metal.
Update the ARM target tuples to enable bare-metal targets.
Add two ARM bare-metal samples.
Add latest Linux kernel versions.

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