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 if [ -z "${CT_NO_OVERIDE_LC_MESSAGES}" ]; then
34 # remove . from PATH since it can cause gcc build failures
37 # Some sanity checks in the environment and needed tools
38 CT_DoLog INFO "Performing some trivial sanity checks"
39 CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
40 CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
41 CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
42 CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
45 # Some sanity checks on paths content
52 eval dir="\${CT_${d}_DIR}"
55 CT_Abort "'CT_${d}_DIR'='${dir}' contains a space in it.\nDon't use spaces in paths, it breaks things."
61 CT_WORK_DIR="${CT_WORK_DIR:-${CT_TOP_DIR}/targets}"
62 CT_DoExecLog ALL mkdir -p "${CT_WORK_DIR}"
64 # Check build file system case-sensitiveness
65 CT_DoExecLog DEBUG touch "${CT_WORK_DIR}/foo"
66 CT_TestAndAbort "Your file system in '${CT_WORK_DIR}' is *not* case-sensitive!" -f "${CT_WORK_DIR}/FOO"
67 CT_DoExecLog DEBUG rm -f "${CT_WORK_DIR}/foo"
70 # Will be plain /bin/sh on most systems, except if we have /bin/ash and we
71 # _explictly_ required using it
72 case "${CT_CONFIG_SHELL}" in
73 sh) CT_SHELL="/bin/sh";;
74 ash) CT_SHELL="/bin/ash";;
75 bash) CT_SHELL="${BASH}";;
76 custom) CT_SHELL="${CT_CONFIG_SHELL_CUSTOM_PATH}";;
79 # Check the user is using an existing SHELL to be used by ./configure and Makefiles
80 CT_TestOrAbort "The CONFIG_SHELL '${CT_CONFIG_SHELL}' (${CT_SHELL}) is not valid" -f "${CT_SHELL}" -a -x "${CT_SHELL}"
82 # Create the bin-overide early
83 # Contains symlinks to the tools found by ./configure
84 # Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so
85 # they can be safely used
86 CT_TOOLS_OVERIDE_DIR="${CT_WORK_DIR}/tools"
87 CT_DoLog DEBUG "Creating bin-overide for tools in '${CT_TOOLS_OVERIDE_DIR}'"
88 CT_DoExecLog DEBUG mkdir -p "${CT_TOOLS_OVERIDE_DIR}/bin"
89 cat "${CT_LIB_DIR}/paths.mk" |while read trash line; do
92 CT_DoLog DEBUG "Creating script-override for '${tool}' -> '${path}'"
93 printf "#${BANG}${CT_SHELL}\nexec '${path}' \"\${@}\"\n" >"${CT_TOOLS_OVERIDE_DIR}/bin/${tool}"
94 CT_DoExecLog ALL chmod 700 "${CT_TOOLS_OVERIDE_DIR}/bin/${tool}"
96 export PATH="${CT_TOOLS_OVERIDE_DIR}/bin:${PATH}"
98 # Start date. Can't be done until we know the locale
99 # Also requires the bin-override tools
100 CT_STAR_DATE=$(CT_DoDate +%s%N)
101 CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
103 # Log real begining of build, now
104 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
106 CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
107 CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
110 CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
114 CT_DoLog INFO "Building environment variables"
116 # Include sub-scripts instead of calling them: that way, we do not have to
117 # export any variable, nor re-parse the configuration and functions files.
118 . "${CT_LIB_DIR}/scripts/build/internals.sh"
119 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
120 . "${CT_LIB_DIR}/scripts/build/companion_tools.sh"
121 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
122 . "${CT_LIB_DIR}/scripts/build/companion_libs/gmp.sh"
123 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpfr.sh"
124 . "${CT_LIB_DIR}/scripts/build/companion_libs/ppl.sh"
125 . "${CT_LIB_DIR}/scripts/build/companion_libs/cloog.sh"
126 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpc.sh"
127 . "${CT_LIB_DIR}/scripts/build/companion_libs/libelf.sh"
128 . "${CT_LIB_DIR}/scripts/build/binutils/binutils.sh"
129 . "${CT_LIB_DIR}/scripts/build/binutils/elf2flt.sh"
130 . "${CT_LIB_DIR}/scripts/build/binutils/sstrip.sh"
131 . "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
132 . "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
133 . "${CT_LIB_DIR}/scripts/build/debug.sh"
134 . "${CT_LIB_DIR}/scripts/build/test_suite.sh"
136 # Target tuple: CT_TARGET needs a little love:
137 CT_DoBuildTargetTuple
139 # Kludge: If any of the configured options needs CT_TARGET,
140 # then rescan the options file now:
143 # Sanity check some directories
144 CT_TestAndAbort "'CT_PREFIX_DIR' is not set: where should I install?" -z "${CT_PREFIX_DIR}"
146 # Second kludge: merge user-supplied target CFLAGS with architecture-provided
147 # target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
148 # Put user-supplied flags at the end, so that they take precedence.
149 CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
150 CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
151 CT_CC_CORE_EXTRA_CONFIG="${CT_ARCH_CC_CORE_EXTRA_CONFIG} ${CT_CC_CORE_EXTRA_CONFIG}"
152 CT_CC_EXTRA_CONFIG="${CT_ARCH_CC_EXTRA_CONFIG} ${CT_CC_EXTRA_CONFIG}"
154 # Compute the working directories names
155 CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
156 CT_SRC_DIR="${CT_WORK_DIR}/src"
157 CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
158 CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
159 CT_CONFIG_DIR="${CT_BUILD_DIR}/configs"
160 if [ "${CT_COMPLIBS_SHARED}" = "y" ]; then
161 CT_COMPLIBS_DIR="${CT_PREFIX_DIR}"
162 # Set LD_LIBRARY_PATH to point to prefix/lib so we can find our own
163 # libraries; add as first path, so we get hit first by the dynamic linker
164 CT_SetLibPath "${CT_COMPLIBS_DIR}/lib" first
166 CT_COMPLIBS_DIR="${CT_BUILD_DIR}/static"
169 # Compute test suite install directory
170 CT_TEST_SUITE_DIR=${CT_INSTALL_DIR}/test-suite
172 # Note: we'll always install the core compiler in its own directory, so as to
173 # not mix the two builds: core and final.
174 CT_CC_CORE_STATIC_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-static"
175 CT_CC_CORE_SHARED_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-shared"
177 # We must ensure that we can restart if asked for!
178 if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}" ]; then
179 CT_DoLog ERROR "You asked to restart a non-restartable build"
180 CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
181 CT_DoLog ERROR "in the config options for the previous build, or the state"
182 CT_DoLog ERROR "directory for the previous build was deleted."
183 CT_Abort "I will stop here to avoid any carnage"
186 # If the local tarball directory does not exist, say so, and don't try to save there!
187 if [ "${CT_SAVE_TARBALLS}" = "y" \
188 -a ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
189 CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist."
190 CT_DoLog WARN "Will not save downloaded tarballs to local storage."
194 # Check now if we can write to the destination directory:
195 if [ -d "${CT_INSTALL_DIR}" ]; then
196 CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
199 # Good, now grab a bit of informations on the system we're being run on,
200 # just in case something goes awok, and it's not our fault:
201 CT_SYS_USER=$(id -un)
202 CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
203 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
204 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
205 CT_SYS_KERNEL=$(uname -s)
206 CT_SYS_REVISION=$(uname -r)
207 CT_SYS_OS=$(uname -s)
208 CT_SYS_MACHINE=$(uname -m)
209 CT_SYS_PROCESSOR=$(uname -p)
210 CT_SYS_GCC=$(gcc -dumpversion)
211 CT_SYS_TARGET=$(CT_DoConfigGuess)
212 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
214 CT_DoLog EXTRA "Preparing working directories"
216 # Ah! The build directory shall be eradicated, even if we restart!
217 if [ -d "${CT_BUILD_DIR}" ]; then
218 CT_DoForceRmdir "${CT_BUILD_DIR}"
221 # Don't eradicate directories if we need to restart
222 if [ -z "${CT_RESTART}" ]; then
223 # Get rid of pre-existing installed toolchain and previous build directories.
224 # We need to do that _before_ we can safely log, because the log file will
225 # most probably be in the toolchain directory.
226 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
227 CT_DoForceRmdir "${CT_TARBALLS_DIR}"
229 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
230 CT_DoForceRmdir "${CT_SRC_DIR}"
232 if [ -d "${CT_INSTALL_DIR}" ]; then
233 CT_DoForceRmdir "${CT_INSTALL_DIR}"
235 # In case we start anew, get rid of the previously saved state directory
236 if [ -d "${CT_STATE_DIR}" ]; then
237 CT_DoForceRmdir "${CT_STATE_DIR}"
241 # Create the directories we'll use, even if restarting: it does no harm to
242 # create already existent directories, and CT_BUILD_DIR needs to be created
244 CT_DoExecLog ALL mkdir -p "${CT_TARBALLS_DIR}"
245 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
246 CT_DoExecLog ALL mkdir -p "${CT_BUILD_DIR}"
247 CT_DoExecLog ALL mkdir -p "${CT_CONFIG_DIR}"
248 CT_DoExecLog ALL mkdir -p "${CT_INSTALL_DIR}"
249 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}"
250 CT_DoExecLog ALL mkdir -p "${CT_COMPLIBS_DIR}"
251 if [ -z "${CT_CANADIAN}" ]; then
252 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_STATIC_PREFIX_DIR}"
253 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_SHARED_PREFIX_DIR}"
256 # Only create the state dir if asked for a restartable build
257 [ -n "${CT_DEBUG_CT_SAVE_STEPS}" ] && CT_DoExecLog ALL mkdir -p "${CT_STATE_DIR}"
259 # Check install file system case-sensitiveness
260 CT_DoExecLog DEBUG touch "${CT_PREFIX_DIR}/foo"
261 CT_TestAndAbort "Your file system in '${CT_PREFIX_DIR}' is *not* case-sensitive!" -f "${CT_PREFIX_DIR}/FOO"
262 CT_DoExecLog DEBUG rm -f "${CT_PREFIX_DIR}/foo"
264 # Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
265 # the previous build was successful. To be able to move the logfile there,
266 # switch them back to read/write
267 CT_DoExecLog ALL chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
269 # Redirect log to the actual log file now we can
270 # It's quite understandable that the log file will be installed in the install
271 # directory, so we must first ensure it exists and is writeable (above) before
274 case "${CT_LOG_TO_FILE}" in
275 y) CT_LOG_FILE="${CT_PREFIX_DIR}/build.log"
276 cat "${tmp_log_file}" >>"${CT_LOG_FILE}"
277 rm -f "${tmp_log_file}"
278 exec >>"${CT_LOG_FILE}"
280 *) rm -f "${tmp_log_file}"
284 # Setting up the rest of the environment only if not restarting
285 if [ -z "${CT_RESTART}" ]; then
286 # Arrange paths depending on wether we use sys-root or not.
287 if [ "${CT_USE_SYSROOT}" = "y" ]; then
288 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root"
289 CT_DEBUGROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/debug-root"
290 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
291 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
292 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
293 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
295 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
296 # confused when $sysroot/usr/include is not present.
297 # Note: --prefix=/usr is magic!
298 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
300 # plain old way. All libraries in prefix/target/lib
301 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
302 CT_DEBUGROOT_DIR="${CT_SYSROOT_DIR}"
303 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
304 # hack! Always use --with-sysroot for binutils.
305 # binutils 2.14 and later obey it, older binutils ignore it.
306 # Lets you build a working 32->64 bit cross gcc
307 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
308 # Use --with-headers, else final gcc will define disable_glibc while
309 # building libgcc, and you'll have no profiling
310 CC_CORE_SYSROOT_ARG="--without-headers"
311 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
312 LIBC_SYSROOT_ARG="prefix="
314 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}"
315 CT_DoExecLog ALL mkdir -p "${CT_DEBUGROOT_DIR}"
317 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
318 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail
319 # with: "ld: cannot open crti.o: No such file or directory"
320 # Also prepare the lib directory in the install dir, else some 64 bit archs
322 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/lib"
323 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/lib"
324 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
325 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/include"
327 if [ "${CT_USE_SYSROOT}" = "y" ]; then
328 # Prevent gcc from installing its libraries outside of the sys-root
329 CT_DoExecLog ALL ln -sf "./${CT_SYSROOT_DIR_PREFIX}/sys-root/lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib"
332 # Since we're *not* multilib on the target side, we want all the
333 # libraries to end up in "lib". We create "lib64" (for 64-bit
334 # build or host architectures) and "lib32" (for 32-bit emulation
335 # on 64-bit) as symlinks to "lib".
337 # Not all of these symlinks are necessary, but better safe than
338 # sorry. They are summarily removed by build/internals.sh:do_finish.
341 "${CT_SYSROOT_DIR}" \
342 "${CT_SYSROOT_DIR}/usr" \
343 "${CT_PREFIX_DIR}/${CT_TARGET}" \
345 CT_DoExecLog ALL ln -sf "lib" "${d}/lib32"
346 CT_DoExecLog ALL ln -sf "lib" "${d}/lib64"
349 # Determine build system if not set by the user
350 if [ -z "${CT_BUILD}" ]; then
351 CT_BUILD=$(CT_DoConfigGuess)
354 # Prepare mangling patterns to later modify BUILD and HOST (see below)
355 case "${CT_TOOLCHAIN_TYPE}" in
357 # A cross-compiler runs on the same machine it is built on
358 CT_HOST="${CT_BUILD}"
359 build_mangle="build_"
362 install_build_tools_for="BUILD HOST"
365 build_mangle="build_"
368 install_build_tools_for="BUILD HOST TARGET"
370 *) CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
374 # Save the real tuples to generate shell-wrappers to the real tools
375 CT_REAL_BUILD="${CT_BUILD}"
376 CT_REAL_HOST="${CT_HOST}"
377 CT_REAL_TARGET="${CT_TARGET}"
379 # Canonicalise CT_BUILD and CT_HOST
380 # Not only will it give us full-qualified tuples, but it will also ensure
381 # that they are valid tuples (in case of typo with user-provided tuples)
382 # That's way better than trying to rewrite config.sub ourselves...
383 # CT_TARGET is already made canonical in CT_DoBuildTargetTuple
384 CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
385 CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
387 # Modify BUILD and HOST so that gcc always generate a cross-compiler
388 # even if any of the build, host or target machines are the same.
389 # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
390 # support canadain build, later...
391 CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
392 CT_HOST="${CT_HOST/-/-${host_mangle}}"
393 CT_TARGET="${CT_TARGET/-/-${target_mangle}}"
395 # Now we have mangled our BUILD and HOST tuples, we must fake the new
396 # cross-tools for those mangled tuples.
397 CT_DoLog DEBUG "Making build system tools available"
398 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/buildtools"
399 for m in ${install_build_tools_for}; do
404 if [ -n "${!p}" ]; then
410 for tool in ar as dlltool gcc g++ gcj gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
411 # First try with prefix + suffix
412 # Then try with prefix only
413 # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
414 # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
415 # This is needed, because some tools have a prefix and
416 # a suffix (eg. gcc), while others may have only one,
417 # or even none (eg. binutils)
418 where=$(CT_Which "${t}${tool}${!s}")
419 [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
421 -a \( "${m}" = "BUILD" \
422 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
423 where=$(CT_Which "${tool}${!s}")
426 -a \( "${m}" = "BUILD" \
427 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
428 where=$(CT_Which "${tool}")
431 # Not all tools are available for all platforms, but some are really,
433 if [ -n "${where}" ]; then
434 CT_DoLog DEBUG " '${!v}-${tool}' -> '${where}'"
435 printf "#${BANG}${CT_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_PREFIX_DIR}/buildtools/${!v}-${tool}"
436 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/buildtools/${!v}-${tool}"
439 # We'll at least need some of them...
440 ar|as|gcc|ld|nm|objcopy|objdump|ranlib)
441 CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
443 # Some are conditionnally required
444 # Add them in alphabetical (C locale) ordering
446 # g++ (needed for companion lib), only needed for HOST
447 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${m}" = "HOST"
450 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_CC_LANG_JAVA}" = "y"
453 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES}" = "y"
455 # If any other is missing, only warn at low level
457 # It does not deserve a WARN level.
458 CT_DoLog DEBUG " Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
465 # Carefully add paths in the order we want them:
466 # - first try in ${CT_PREFIX_DIR}/bin
467 # - then try in ${CT_CC_CORE_SHARED_PREFIX_DIR}/bin
468 # - then try in ${CT_CC_CORE_STATIC_PREFIX_DIR}/bin
469 # - fall back to searching user's PATH
470 # Of course, neither cross-native nor canadian can run on BUILD,
471 # so don't add those PATHs in this case...
472 case "${CT_TOOLCHAIN_TYPE}" in
473 cross) export PATH="${CT_PREFIX_DIR}/buildtools:${CT_PREFIX_DIR}/bin:${CT_CC_CORE_SHARED_PREFIX_DIR}/bin:${CT_CC_CORE_STATIC_PREFIX_DIR}/bin:${PATH}";;
474 canadian) export PATH="${CT_PREFIX_DIR}/buildtools:${PATH}";;
478 # Some makeinfo versions are a pain in [put your most sensible body part here].
479 # Go ahead with those, by creating a wrapper that keeps partial files, and that
481 CT_DoLog DEBUG " 'makeinfo' -> '$(CT_Which makeinfo)'"
482 printf "#${BANG}${CT_SHELL}\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue\n" >"${CT_PREFIX_DIR}/buildtools/makeinfo"
483 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/buildtools/makeinfo"
487 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
489 # Override the configured jobs with what's been given on the command line
490 [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
492 # Set the shell to be used by ./configure scripts and by Makefiles (those
494 export CONFIG_SHELL="${CT_SHELL}" # for ./configure
495 export SHELL="${CT_SHELL}" # for Makefiles
497 # And help make go faster
499 [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
500 [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
501 export PARALLELMFLAGS
503 CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
504 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/bin"
505 CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/scripts/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
506 CT_DoExecLog DEBUG sed -i -e 's,@@grep@@,"'"${grep}"'",;' "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
507 bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
509 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
510 CT_DoLog EXTRA "Building a toolchain for:"
511 CT_DoLog EXTRA " build = ${CT_REAL_BUILD}"
512 CT_DoLog EXTRA " host = ${CT_REAL_HOST}"
513 CT_DoLog EXTRA " target = ${CT_TARGET}"
514 set |grep -E '^CT_.+=' |sort |CT_DoLog DEBUG
515 CT_DoLog DEBUG "Other environment:"
516 printenv |grep -v -E '^CT_.+=' |CT_DoLog DEBUG
520 if [ -z "${CT_RESTART}" ]; then
521 if [ "${CT_FORBID_DOWNLOAD}" = "y" ]; then
522 CT_DoLog INFO "Downloading forbidden by configuration, skipping downloads"
524 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
525 do_companion_tools_get
543 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
544 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
545 CT_DoForceRmdir "${CT_SRC_DIR}"
546 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
549 if [ "${CT_COMP_TOOLS}" = "y" ]; then
550 CT_DoStep INFO "Extracting, patching and installing companion tools"
551 do_companion_tools_extract
556 CT_DoStep INFO "Extracting and patching toolchain components"
570 do_test_suite_extract
575 # Now for the job by itself. Go have a coffee!
576 if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
577 # Because of CT_RESTART, this becomes quite complex
580 [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
581 # Aha! CT_STEPS comes from steps.mk!
582 for step in ${CT_STEPS}; do
583 if [ ${do_it} -eq 0 ]; then
584 if [ "${CT_RESTART}" = "${step}" ]; then
585 CT_DoLoadState "${step}"
590 CT_DoSaveState ${step}
591 if [ ${do_stop} -eq 1 ]; then
592 CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
596 if [ ${do_it} -eq 1 ]; then
598 if [ "${CT_STOP}" = "${step}" ]; then
601 if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
602 CT_DoPause "Step '${step}' finished"
611 # From now-on, it can become impossible to log any time, because
612 # either we're compressing the log file, or it can become RO any
613 # moment... Consign all ouptut to oblivion...
614 CT_DoLog INFO "Finishing installation (may take a few seconds)..."
617 [ "${CT_LOG_FILE_COMPRESS}" = y ] && bzip2 -9 "${CT_LOG_FILE}"
618 [ "${CT_INSTALL_DIR_RO}" = "y" ] && chmod -R a-w "${CT_INSTALL_DIR}"
619 [ "${CT_TEST_SUITE}" = "y" ] && chmod -R u+w "${CT_TEST_SUITE_DIR}"