2 # Copyright 2007 Yann E. MORIN
3 # Licensed under the GPL v2. See COPYING in the root of this package.
5 # This is the main entry point to crosstool
7 # - download, extract and patch the toolchain components
8 # - build and install each components in turn
9 # - and eventually test the resulting toolchain
11 # What this file does is prepare the environment, based upon the user-choosen
12 # options. It also checks the existing environment for un-friendly variables,
13 # and builds the tools.
15 # Parse the common functions
16 # Note: some initialisation and sanitizing is done while parsing this file,
18 # - set trap handler on errors,
19 # - don't hash commands lookups,
20 # - initialise logging.
21 . "${CT_LIB_DIR}/scripts/functions"
23 # Parse the configuration file
24 # It has some info about the logging facility, so include it early
26 # Yes! We can do full logging from now on!
28 # Overide the locale early, in case we ever translate crosstool-NG messages
29 [ -z "${CT_NO_OVERIDE_LC_MESSAGES}" ] && export LC_ALL=C
31 # Some sanity checks in the environment and needed tools
32 CT_DoLog INFO "Performing some trivial sanity checks"
33 CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
34 CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
35 CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
36 CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
39 # Some sanity checks on paths content
46 eval dir="\${CT_${d}_DIR}"
49 CT_Abort "'CT_${d}_DIR'='${dir}' contains a space in it.\nDon't use spaces in paths, it breaks things."
55 CT_WORK_DIR="${CT_WORK_DIR:-${CT_TOP_DIR}/targets}"
56 CT_DoExecLog ALL mkdir -p "${CT_WORK_DIR}"
58 # Check build file system case-sensitiveness
59 CT_DoExecLog DEBUG touch "${CT_WORK_DIR}/foo"
60 CT_TestAndAbort "Your file system in '${CT_WORK_DIR}' is *not* case-sensitive!" -f "${CT_WORK_DIR}/FOO"
61 CT_DoExecLog DEBUG rm -f "${CT_WORK_DIR}/foo"
63 # Create the bin-overide early
64 # Contains symlinks to the tools found by ./configure
65 # Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so
66 # they can be safely used
67 CT_BIN_OVERIDE_DIR="${CT_WORK_DIR}/bin"
68 CT_DoLog DEBUG "Creating bin-overide for tools in '${CT_BIN_OVERIDE_DIR}'"
69 CT_DoExecLog DEBUG mkdir -p "${CT_BIN_OVERIDE_DIR}"
70 cat "${CT_LIB_DIR}/paths.mk" |while read trash line; do
73 CT_DoLog DEBUG " '${tool}' -> '${path}'"
74 printf "#${BANG}/bin/sh\nexec '${path}' \"\${@}\"\n" >"${CT_BIN_OVERIDE_DIR}/${tool}"
75 CT_DoExecLog ALL chmod 700 "${CT_BIN_OVERIDE_DIR}/${tool}"
77 export PATH="${CT_BIN_OVERIDE_DIR}:${PATH}"
79 # Start date. Can't be done until we know the locale
80 # Also requires the bin-override tools
81 CT_STAR_DATE=$(CT_DoDate +%s%N)
82 CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
84 # Log real begining of build, now
85 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
88 CT_DoExecLog DEBUG renice ${CT_NICE} $$
90 CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
91 CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
94 CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
98 CT_DoLog INFO "Building environment variables"
100 # Include sub-scripts instead of calling them: that way, we do not have to
101 # export any variable, nor re-parse the configuration and functions files.
102 . "${CT_LIB_DIR}/scripts/build/internals.sh"
103 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
104 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
105 . "${CT_LIB_DIR}/scripts/build/companion_libs/gmp.sh"
106 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpfr.sh"
107 . "${CT_LIB_DIR}/scripts/build/companion_libs/ppl.sh"
108 . "${CT_LIB_DIR}/scripts/build/companion_libs/cloog.sh"
109 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpc.sh"
110 . "${CT_LIB_DIR}/scripts/build/binutils/binutils.sh"
111 . "${CT_LIB_DIR}/scripts/build/binutils/elf2flt.sh"
112 . "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
113 . "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
114 . "${CT_LIB_DIR}/scripts/build/tools.sh"
115 . "${CT_LIB_DIR}/scripts/build/debug.sh"
117 # Target tuple: CT_TARGET needs a little love:
118 CT_DoBuildTargetTuple
120 # Kludge: If any of the configured options needs CT_TARGET,
121 # then rescan the options file now:
124 # Second kludge: merge user-supplied target CFLAGS with architecture-provided
125 # target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
126 # Put user-supplied flags at the end, so that they take precedence.
127 CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
128 CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
129 CT_CC_CORE_EXTRA_CONFIG="${CT_ARCH_CC_CORE_EXTRA_CONFIG} ${CT_CC_CORE_EXTRA_CONFIG}"
130 CT_CC_EXTRA_CONFIG="${CT_ARCH_CC_EXTRA_CONFIG} ${CT_CC_EXTRA_CONFIG}"
132 # Compute the working directories names
133 CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
134 CT_SRC_DIR="${CT_WORK_DIR}/src"
135 CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
136 CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
137 CT_CONFIG_DIR="${CT_BUILD_DIR}/configs"
139 # Note: we'll always install the core compiler in its own directory, so as to
140 # not mix the two builds: core and final.
141 CT_CC_CORE_STATIC_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-static"
142 CT_CC_CORE_SHARED_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-shared"
144 # Set LD_LIBRARY_PATH to point to prefix/lib so we can find our own
145 # libraries; add as first path, so we get hit first by the dynamic linker
146 CT_SetLibPath "${CT_PREFIX_DIR}/lib" first
148 # We must ensure that we can restart if asked for!
149 if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}" ]; then
150 CT_DoLog ERROR "You asked to restart a non-restartable build"
151 CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
152 CT_DoLog ERROR "in the config options for the previous build, or the state"
153 CT_DoLog ERROR "directory for the previous build was deleted."
154 CT_Abort "I will stop here to avoid any carnage"
157 # If the local tarball directory does not exist, say so, and don't try to save there!
158 if [ ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
159 CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist. Will not save downloaded tarballs to local storage."
163 # Check now if we can write to the destination directory:
164 if [ -d "${CT_INSTALL_DIR}" ]; then
165 CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
168 # Good, now grab a bit of informations on the system we're being run on,
169 # just in case something goes awok, and it's not our fault:
170 CT_SYS_USER=$(id -un)
171 CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
172 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
173 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
174 CT_SYS_KERNEL=$(uname -s)
175 CT_SYS_REVISION=$(uname -r)
176 # MacOS X lacks '-o' :
177 CT_SYS_OS=$(uname -o || echo "Unknown (maybe MacOS-X)")
178 CT_SYS_MACHINE=$(uname -m)
179 CT_SYS_PROCESSOR=$(uname -p)
180 CT_SYS_GCC=$(gcc -dumpversion)
181 CT_SYS_TARGET=$(CT_DoConfigGuess)
182 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
184 CT_DoLog EXTRA "Preparing working directories"
186 # Ah! The build directory shall be eradicated, even if we restart!
187 if [ -d "${CT_BUILD_DIR}" ]; then
188 CT_DoForceRmdir "${CT_BUILD_DIR}"
191 # Don't eradicate directories if we need to restart
192 if [ -z "${CT_RESTART}" ]; then
193 # Get rid of pre-existing installed toolchain and previous build directories.
194 # We need to do that _before_ we can safely log, because the log file will
195 # most probably be in the toolchain directory.
196 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
197 CT_DoForceRmdir "${CT_TARBALLS_DIR}"
199 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
200 CT_DoForceRmdir "${CT_SRC_DIR}"
202 if [ -d "${CT_INSTALL_DIR}" ]; then
203 CT_DoForceRmdir "${CT_INSTALL_DIR}"
205 # In case we start anew, get rid of the previously saved state directory
206 if [ -d "${CT_STATE_DIR}" ]; then
207 CT_DoForceRmdir "${CT_STATE_DIR}"
211 # Create the directories we'll use, even if restarting: it does no harm to
212 # create already existent directories, and CT_BUILD_DIR needs to be created
214 CT_DoExecLog ALL mkdir -p "${CT_TARBALLS_DIR}"
215 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
216 CT_DoExecLog ALL mkdir -p "${CT_BUILD_DIR}"
217 CT_DoExecLog ALL mkdir -p "${CT_CONFIG_DIR}"
218 CT_DoExecLog ALL mkdir -p "${CT_INSTALL_DIR}"
219 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}"
220 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_STATIC_PREFIX_DIR}"
221 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_SHARED_PREFIX_DIR}"
223 # Only create the state dir if asked for a restartable build
224 [ -n "${CT_DEBUG_CT_SAVE_STEPS}" ] && CT_DoExecLog ALL mkdir -p "${CT_STATE_DIR}"
226 # Check install file system case-sensitiveness
227 CT_DoExecLog DEBUG touch "${CT_PREFIX_DIR}/foo"
228 CT_TestAndAbort "Your file system in '${CT_PREFIX_DIR}' is *not* case-sensitive!" -f "${CT_PREFIX_DIR}/FOO"
229 CT_DoExecLog DEBUG rm -f "${CT_PREFIX_DIR}/foo"
231 # Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
232 # the previous build was successful. To be able to move the logfile there,
233 # switch them back to read/write
234 CT_DoExecLog ALL chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
236 # Redirect log to the actual log file now we can
237 # It's quite understandable that the log file will be installed in the install
238 # directory, so we must first ensure it exists and is writeable (above) before
241 case "${CT_LOG_TO_FILE}" in
242 y) CT_LOG_FILE="${CT_PREFIX_DIR}/build.log"
243 cat "${tmp_log_file}" >>"${CT_LOG_FILE}"
244 rm -f "${tmp_log_file}"
245 exec >>"${CT_LOG_FILE}"
247 *) rm -f "${tmp_log_file}"
251 # Setting up the rest of the environment only if not restarting
252 if [ -z "${CT_RESTART}" ]; then
254 # Will be plain /bin/sh on most systems, except if we have /bin/ash and we
255 # _explictly_ required using it
257 [ "${CT_CONFIG_SHELL_ASH}" = "y" -a -x "/bin/ash" ] && CT_SHELL="/bin/ash"
259 # Arrange paths depending on wether we use sys-root or not.
260 if [ "${CT_USE_SYSROOT}" = "y" ]; then
261 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root"
262 CT_DEBUGROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/debug-root"
263 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
264 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
265 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
266 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
268 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
269 # confused when $sysroot/usr/include is not present.
270 # Note: --prefix=/usr is magic!
271 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
273 # plain old way. All libraries in prefix/target/lib
274 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
275 CT_DEBUGROOT_DIR="${CT_SYSROOT_DIR}"
276 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
277 # hack! Always use --with-sysroot for binutils.
278 # binutils 2.14 and later obey it, older binutils ignore it.
279 # Lets you build a working 32->64 bit cross gcc
280 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
281 # Use --with-headers, else final gcc will define disable_glibc while
282 # building libgcc, and you'll have no profiling
283 CC_CORE_SYSROOT_ARG="--without-headers"
284 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
285 LIBC_SYSROOT_ARG="prefix="
287 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}"
288 CT_DoExecLog ALL mkdir -p "${CT_DEBUGROOT_DIR}"
290 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
291 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail
292 # with: "ld: cannot open crti.o: No such file or directory"
293 # Also prepare the lib directory in the install dir, else some 64 bit archs
295 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/lib"
296 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/lib"
297 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
299 if [ "${CT_USE_SYSROOT}" = "y" ]; then
300 # Prevent gcc from installing its libraries outside of the sys-root
301 CT_DoExecLog ALL ln -sf "./${CT_SYSROOT_DIR_PREFIX}/sys-root/lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib"
304 # Now, in case we're 64 bits, just have lib64/ be a symlink to lib/
305 # so as to have all libraries in the same directory (we can do that
306 # because we are *not* multilib).
307 if [ "${CT_ARCH_64}" = "y" ]; then
308 CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/lib64"
309 CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/lib64"
310 CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/usr/lib64"
311 CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib64"
314 # Determine build system if not set by the user
315 CT_Test "You did not specify the build system. That's OK, I can guess..." -z "${CT_BUILD}"
316 case "${CT_BUILD}" in
317 "") CT_BUILD=$("${CT_BUILD_PREFIX}gcc${CT_BUILD_SUFFIX}" -dumpmachine);;
320 # Prepare mangling patterns to later modify BUILD and HOST (see below)
321 case "${CT_TOOLCHAIN_TYPE}" in
323 CT_HOST="${CT_BUILD}"
324 build_mangle="build_"
327 *) CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
331 # Save the real tuples to generate shell-wrappers to the real tools
332 CT_REAL_BUILD="${CT_BUILD}"
333 CT_REAL_HOST="${CT_HOST}"
335 # Canonicalise CT_BUILD and CT_HOST
336 # Not only will it give us full-qualified tuples, but it will also ensure
337 # that they are valid tuples (in case of typo with user-provided tuples)
338 # That's way better than trying to rewrite config.sub ourselves...
339 CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
340 CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
342 # Modify BUILD and HOST so that gcc always generate a cross-compiler
343 # even if any of the build, host or target machines are the same.
344 # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
345 # support canadain build, later...
346 CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
347 CT_HOST="${CT_HOST/-/-${host_mangle}}"
349 # Now we have mangled our BUILD and HOST tuples, we must fake the new
350 # cross-tools for those mangled tuples.
351 CT_DoLog DEBUG "Making build system tools available"
352 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/bin"
353 for m in BUILD HOST; do
358 if [ -n "${!p}" ]; then
364 for tool in ar as dlltool gcc g++ gcj gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
365 # First try with prefix + suffix
366 # Then try with prefix only
367 # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
368 # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
369 # This is needed, because some tools have a prefix and
370 # a suffix (eg. gcc), while others may have only one,
371 # or even none (eg. binutils)
372 where=$(CT_Which "${t}${tool}${!s}")
373 [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
375 -a \( "${m}" = "BUILD" \
376 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
377 where=$(CT_Which "${tool}${!s}")
380 -a \( "${m}" = "BUILD" \
381 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
382 where=$(CT_Which "${tool}")
385 # Not all tools are available for all platforms, but some are really,
387 if [ -n "${where}" ]; then
388 CT_DoLog DEBUG " '${!v}-${tool}' -> '${where}'"
389 printf "#${BANG}${CT_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_PREFIX_DIR}/bin/${!v}-${tool}"
390 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/bin/${!v}-${tool}"
393 # We'll at least need some of them...
394 ar|as|gcc|ld|nm|objcopy|objdump|ranlib)
395 CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
397 # Some are conditionnally required
398 # Add them in alphabetical (C locale) ordering
400 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_CC_LANG_JAVA}" = "y"
402 # If any other is missing, only warn at low level
404 # It does not deserve a WARN level.
405 CT_DoLog DEBUG " Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
412 # Carefully add paths in the order we want them:
413 # - first try in ${CT_PREFIX_DIR}/bin
414 # - then try in ${CT_CC_CORE_SHARED_PREFIX_DIR}/bin
415 # - then try in ${CT_CC_CORE_STATIC_PREFIX_DIR}/bin
416 # - fall back to searching user's PATH
417 # Of course, neither cross-native nor canadian can run on BUILD,
418 # so don't add those PATHs in this case...
419 case "${CT_TOOLCHAIN_TYPE}" in
420 cross) export PATH="${CT_PREFIX_DIR}/bin:${CT_CC_CORE_SHARED_PREFIX_DIR}/bin:${CT_CC_CORE_STATIC_PREFIX_DIR}/bin:${PATH}";;
424 # Some makeinfo versions are a pain in [put your most sensible body part here].
425 # Go ahead with those, by creating a wrapper that keeps partial files, and that
427 CT_DoLog DEBUG " 'makeinfo' -> '$(CT_Which makeinfo)'"
428 printf "#${BANG}/bin/sh\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue\n" >"${CT_PREFIX_DIR}/bin/makeinfo"
429 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/bin/makeinfo"
433 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
435 # Override the configured jobs with what's been given on the command line
436 [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
438 # Set the shell to be used by ./configure scripts and by Makefiles (those
440 export CONFIG_SHELL="${CT_SHELL}"
442 # And help make go faster
444 [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
445 [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
446 export PARALLELMFLAGS
448 CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
449 CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/scripts/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
450 CT_DoExecLog DEBUG sed -r -i -e 's,@@grep@@,"'"${grep}"'",;' "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
451 bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
453 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
454 CT_DoLog EXTRA "Building a toolchain for:"
455 CT_DoLog EXTRA " build = ${CT_REAL_BUILD}"
456 CT_DoLog EXTRA " host = ${CT_REAL_HOST}"
457 CT_DoLog EXTRA " target = ${CT_TARGET}"
458 set |grep -E '^CT_.+=' |sort |CT_DoLog DEBUG
462 if [ -z "${CT_RESTART}" ]; then
463 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
477 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
478 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
479 CT_DoForceRmdir "${CT_SRC_DIR}"
480 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
482 CT_DoStep INFO "Extracting and patching toolchain components"
498 # Now for the job by itself. Go have a coffee!
499 if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
500 # Because of CT_RESTART, this becomes quite complex
503 [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
504 # Aha! CT_STEPS comes from steps.mk!
505 for step in ${CT_STEPS}; do
506 if [ ${do_it} -eq 0 ]; then
507 if [ "${CT_RESTART}" = "${step}" ]; then
508 CT_DoLoadState "${step}"
513 CT_DoSaveState ${step}
514 if [ ${do_stop} -eq 1 ]; then
515 CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
519 if [ ${do_it} -eq 1 ]; then
521 if [ "${CT_STOP}" = "${step}" ]; then
524 if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
525 CT_DoPause "Step '${step}' finished"
534 # From now-on, it can become impossible to log any time, because
535 # either we're compressing the log file, or it can become RO any
536 # moment... Consign all ouptut to oblivion...
537 CT_DoLog INFO "Finishing installation (may take a few seconds)..."
540 [ "${CT_LOG_FILE_COMPRESS}" = y ] && bzip2 -9 "${CT_LOG_FILE}"
541 [ "${CT_INSTALL_DIR_RO}" = "y" ] && chmod -R a-w "${CT_INSTALL_DIR}"