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 # If we want an interactive debug-shell, we must ensure these FDs
29 # are indeed connected to a terminal (and not redirected in any way).
30 if [ "${CT_DEBUG_INTERACTIVE}" = "y" -a ! \( -t 0 -a -t 6 -a -t 2 \) ]; then
31 CT_DoLog ERROR "Can't spawn interactive debug-shell,"
32 CT_DoLog ERROR "because stdout/stderr has been redirected."
36 # Override the locale early, in case we ever translate crosstool-NG messages
37 if [ -z "${CT_NO_OVERIDE_LC_MESSAGES}" ]; then
42 # remove . from PATH since it can cause gcc build failures
45 # Some sanity checks in the environment and needed tools
46 CT_DoLog INFO "Performing some trivial sanity checks"
47 CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
48 CT_TestAndAbort "Don't set LIBRARY_PATH. It screws up the build." -n "${LIBRARY_PATH}"
49 CT_TestAndAbort "Don't set LPATH. It screws up the build." -n "${LPATH}"
50 CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
51 CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
52 CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
54 # Workaround against openSUSE 12.1 that breaks ./configure for cross-compilation:
57 # Some sanity checks on paths content
64 eval dir="\${CT_${d}_DIR}"
67 CT_Abort "'CT_${d}_DIR'='${dir}' contains a space in it.\nDon't use spaces in paths, it breaks things."
70 CT_Abort "'CT_${d}_DIR'='${dir}' contains a colon in it.\nDon't use colons in paths, it breaks things."
76 CT_WORK_DIR="${CT_WORK_DIR:-${CT_TOP_DIR}/.build}"
77 CT_DoExecLog ALL mkdir -p "${CT_WORK_DIR}"
78 CT_DoExecLog DEBUG rm -f "${CT_WORK_DIR}/backtrace"
80 # Check build file system case-sensitiveness
81 CT_DoExecLog DEBUG touch "${CT_WORK_DIR}/foo"
82 CT_TestAndAbort "Your file system in '${CT_WORK_DIR}' is *not* case-sensitive!" -f "${CT_WORK_DIR}/FOO"
83 CT_DoExecLog DEBUG rm -f "${CT_WORK_DIR}/foo"
85 # Check the user is using an existing SHELL to be used by ./configure and Makefiles
86 CT_TestOrAbort "The CONFIG_SHELL '${CT_CONFIG_SHELL}' is not valid" -f "${CT_CONFIG_SHELL}" -a -x "${CT_CONFIG_SHELL}"
88 # Create the bin-override early
89 # Contains symlinks to the tools found by ./configure
90 # Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so
91 # they can be safely used
92 CT_TOOLS_OVERIDE_DIR="${CT_WORK_DIR}/tools"
93 CT_DoLog DEBUG "Creating bin-override for tools in '${CT_TOOLS_OVERIDE_DIR}'"
94 CT_DoExecLog DEBUG mkdir -p "${CT_TOOLS_OVERIDE_DIR}/bin"
95 cat "${CT_LIB_DIR}/paths.sh" |while read trash line; do
98 CT_DoLog DEBUG "Creating script-override for '${tool}' -> '${path}'"
99 # Note: we need to supress the " in the path because
100 # there can be arguments in there (thanks autostuff...)
101 printf "#${BANG}${CT_CONFIG_SHELL}\nexec ${path//\"/} \"\${@}\"\n" >"${CT_TOOLS_OVERIDE_DIR}/bin/${tool}"
102 CT_DoExecLog ALL chmod 700 "${CT_TOOLS_OVERIDE_DIR}/bin/${tool}"
104 export PATH="${CT_TOOLS_OVERIDE_DIR}/bin:${PATH}"
106 # Start date. Can't be done until we know the locale
107 # Also requires the bin-override tools
108 CT_STAR_DATE=$(CT_DoDate +%s%N)
109 CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
111 # Log real begining of build, now
112 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
114 # We really need to extract from ,config and not .config.2, as we
115 # do want the kconfig's values, not our mangled config with arrays.
116 CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
117 CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
120 CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
124 CT_DoLog INFO "Building environment variables"
126 # Include sub-scripts instead of calling them: that way, we do not have to
127 # export any variable, nor re-parse the configuration and functions files.
128 . "${CT_LIB_DIR}/scripts/build/internals.sh"
129 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
130 . "${CT_LIB_DIR}/scripts/build/companion_tools.sh"
131 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
132 . "${CT_LIB_DIR}/scripts/build/companion_libs/gmp.sh"
133 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpfr.sh"
134 . "${CT_LIB_DIR}/scripts/build/companion_libs/ppl.sh"
135 . "${CT_LIB_DIR}/scripts/build/companion_libs/cloog.sh"
136 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpc.sh"
137 . "${CT_LIB_DIR}/scripts/build/companion_libs/libelf.sh"
138 . "${CT_LIB_DIR}/scripts/build/binutils/binutils.sh"
139 . "${CT_LIB_DIR}/scripts/build/binutils/elf2flt.sh"
140 . "${CT_LIB_DIR}/scripts/build/binutils/sstrip.sh"
141 . "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
142 . "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
143 . "${CT_LIB_DIR}/scripts/build/debug.sh"
144 . "${CT_LIB_DIR}/scripts/build/test_suite.sh"
146 # Target tuple: CT_TARGET needs a little love:
147 CT_DoBuildTargetTuple
149 # Kludge: If any of the configured options needs CT_TARGET,
150 # then rescan the options file now:
153 # Sanity check some directories
154 CT_TestAndAbort "'CT_PREFIX_DIR' is not set: where should I install?" -z "${CT_PREFIX_DIR}"
156 # Second kludge: merge user-supplied target CFLAGS with architecture-provided
157 # target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
158 # Put user-supplied flags at the end, so that they take precedence.
159 CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
160 CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
161 CT_CC_CORE_EXTRA_CONFIG_ARRAY=( ${CT_ARCH_CC_CORE_EXTRA_CONFIG} "${CT_CC_CORE_EXTRA_CONFIG_ARRAY[@]}" )
162 CT_CC_EXTRA_CONFIG_ARRAY=( ${CT_ARCH_CC_EXTRA_CONFIG} "${CT_CC_EXTRA_CONFIG_ARRAY[@]}" )
164 # Compute the package version string
165 CT_PKGVERSION="crosstool-NG ${CT_VERSION}${CT_TOOLCHAIN_PKGVERSION:+ - ${CT_TOOLCHAIN_PKGVERSION}}"
167 # Compute the working directories names
168 CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
169 CT_SRC_DIR="${CT_WORK_DIR}/src"
170 CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
171 CT_BUILDTOOLS_PREFIX_DIR="${CT_WORK_DIR}/${CT_TARGET}/buildtools"
172 CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
173 CT_CONFIG_DIR="${CT_BUILD_DIR}/configs"
174 # Note about HOST_COMPLIBS_DIR: it's always gonna be in the buildtools dir, or a
175 # sub-dir. So we won't have to save/restore it, not even create it.
176 # In case of cross or native, host-complibs are used for build-complibs;
177 # in case of canadian or cross-native, host-complibs are specific
178 case "${CT_TOOLCHAIN_TYPE}" in
180 CT_HOST_COMPLIBS_DIR="${CT_BUILDTOOLS_PREFIX_DIR}"
182 canadian|cross-native)
183 CT_HOST_COMPLIBS_DIR="${CT_BUILDTOOLS_PREFIX_DIR}/complibs-host"
187 # Compute test suite install directory
188 CT_TEST_SUITE_DIR=${CT_INSTALL_DIR}/test-suite
190 # We must ensure that we can restart if asked for!
191 if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}" ]; then
192 CT_DoLog ERROR "You asked to restart a non-restartable build"
193 CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
194 CT_DoLog ERROR "in the config options for the previous build, or the state"
195 CT_DoLog ERROR "directory for the previous build was deleted."
196 CT_Abort "I will stop here to avoid any carnage"
199 # If the local tarball directory does not exist, say so, and don't try to save there!
200 if [ "${CT_SAVE_TARBALLS}" = "y" \
201 -a ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
202 CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist."
203 CT_DoLog WARN "Will not save downloaded tarballs to local storage."
207 # Check now if we can write to the destination directory:
208 if [ -d "${CT_INSTALL_DIR}" ]; then
209 CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
212 # Good, now grab a bit of informations on the system we're being run on,
213 # just in case something goes awok, and it's not our fault:
214 CT_SYS_USER=$(id -un)
215 CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
216 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
217 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
218 CT_SYS_KERNEL=$(uname -s)
219 CT_SYS_REVISION=$(uname -r)
220 CT_SYS_OS=$(uname -s)
221 CT_SYS_MACHINE=$(uname -m)
222 CT_SYS_PROCESSOR=$(uname -p)
223 CT_SYS_GCC=$(gcc -dumpversion)
224 CT_SYS_TARGET=$(CT_DoConfigGuess)
225 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
227 CT_DoLog EXTRA "Preparing working directories"
229 # Ah! The build directory shall be eradicated, even if we restart!
230 # Ditto for the build tools install dir
231 CT_DoForceRmdir "${CT_BUILD_DIR}" "${CT_BUILDTOOLS_PREFIX_DIR}"
233 # Don't eradicate directories if we need to restart
234 if [ -z "${CT_RESTART}" ]; then
235 # Get rid of pre-existing installed toolchain and previous build directories.
236 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
237 CT_DoForceRmdir "${CT_TARBALLS_DIR}"
239 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
240 CT_DoForceRmdir "${CT_SRC_DIR}"
242 if [ -d "${CT_INSTALL_DIR}" -a "${CT_RM_RF_PREFIX_DIR}" = "y" ]; then
243 CT_DoForceRmdir "${CT_INSTALL_DIR}"
245 # In case we start anew, get rid of the previously saved state directory
246 if [ -d "${CT_STATE_DIR}" ]; then
247 CT_DoForceRmdir "${CT_STATE_DIR}"
251 # Create the directories we'll use, even if restarting: it does no harm to
252 # create already existent directories, and CT_BUILD_DIR needs to be created
254 CT_DoExecLog ALL mkdir -p "${CT_TARBALLS_DIR}"
255 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
256 CT_DoExecLog ALL mkdir -p "${CT_BUILD_DIR}"
257 CT_DoExecLog ALL mkdir -p "${CT_BUILDTOOLS_PREFIX_DIR}/bin"
258 CT_DoExecLog ALL mkdir -p "${CT_CONFIG_DIR}"
259 CT_DoExecLog ALL mkdir -p "${CT_INSTALL_DIR}"
260 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}"
261 CT_DoExecLog ALL mkdir -p "${CT_HOST_COMPLIBS_DIR}"
263 # Only create the state dir if asked for a restartable build
264 [ -n "${CT_DEBUG_CT_SAVE_STEPS}" ] && CT_DoExecLog ALL mkdir -p "${CT_STATE_DIR}"
266 # Check install file system case-sensitiveness
267 CT_DoExecLog DEBUG touch "${CT_PREFIX_DIR}/foo"
268 CT_TestAndAbort "Your file system in '${CT_PREFIX_DIR}' is *not* case-sensitive!" -f "${CT_PREFIX_DIR}/FOO"
269 CT_DoExecLog DEBUG rm -f "${CT_PREFIX_DIR}/foo"
271 # Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
272 # the previous build was successful.
273 CT_DoExecLog ALL chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
275 # Setting up the rest of the environment only if not restarting
276 if [ -z "${CT_RESTART}" ]; then
277 case "${CT_SYSROOT_NAME}" in
278 "") CT_SYSROOT_NAME="sysroot";;
279 .) CT_Abort "Sysroot name is set to '.' which is forbidden";;
280 *' '*) CT_Abort "Sysroot name contains forbidden space(s): '${CT_SYSROOT_NAME}'";;
281 */*) CT_Abort "Sysroot name contains forbidden slash(es): '${CT_SYSROOT_NAME}'";;
284 # Arrange paths depending on wether we use sysroot or not.
285 if [ "${CT_USE_SYSROOT}" = "y" ]; then
286 CT_SYSROOT_REL_DIR="${CT_SYSROOT_DIR_PREFIX:+${CT_SYSROOT_DIR_PREFIX}/}${CT_SYSROOT_NAME}"
287 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_REL_DIR}"
288 CT_DEBUGROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/debug-root"
289 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
290 CT_SanitiseVarDir CT_SYSROOT_REL_DIR CT_SYSROOT_DIR CT_DEBUGROOT_DIR CT_HEADERS_DIR
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 CT_SanitiseVarDir CT_SYSROOT_DIR CT_DEBUGROOT_DIR CT_HEADERS_DIR
305 # hack! Always use --with-sysroot for binutils.
306 # binutils 2.14 and later obey it, older binutils ignore it.
307 # Lets you build a working 32->64 bit cross gcc
308 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
309 # Use --with-headers, else final gcc will define disable_glibc while
310 # building libgcc, and you'll have no profiling
311 CC_CORE_SYSROOT_ARG="--without-headers"
312 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
313 LIBC_SYSROOT_ARG="prefix="
315 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}"
316 CT_DoExecLog ALL mkdir -p "${CT_DEBUGROOT_DIR}"
318 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
319 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail
320 # with: "ld: cannot open crti.o: No such file or directory"
321 # Also prepare the lib directory in the install dir, else some 64 bit archs
323 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/lib"
324 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/lib"
325 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
326 CT_DoExecLog ALL mkdir -p "${CT_HEADERS_DIR}"
328 if [ "${CT_USE_SYSROOT}" = "y" ]; then
329 # Prevent gcc from installing its libraries outside of the sysroot
330 CT_Pushd "${CT_PREFIX_DIR}/${CT_TARGET}"
331 CT_DoExecLog ALL ln -sf "${CT_SYSROOT_REL_DIR}/lib" "lib"
335 # Since we're *not* multilib on the target side, we want all the
336 # libraries to end up in "lib". We create "lib64" (for 64-bit
337 # build or host architectures) and "lib32" (for 32-bit emulation
338 # on 64-bit) as symlinks to "lib".
340 # Not all of these symlinks are necessary, but better safe than
341 # sorry. They are summarily removed by build/internals.sh:do_finish.
344 "${CT_SYSROOT_DIR}" \
345 "${CT_SYSROOT_DIR}/usr" \
346 "${CT_PREFIX_DIR}/${CT_TARGET}" \
348 CT_DoExecLog ALL ln -sf "lib" "${d}/lib32"
349 CT_DoExecLog ALL ln -sf "lib" "${d}/lib64"
352 # Determine build system if not set by the user
353 if [ -z "${CT_BUILD}" ]; then
354 CT_BUILD=$(CT_DoConfigGuess)
357 # Prepare mangling patterns to later modify BUILD and HOST (see below)
358 case "${CT_TOOLCHAIN_TYPE}" in
360 # A cross-compiler runs on the same machine it is built on
361 CT_HOST="${CT_BUILD}"
362 build_mangle="build_"
365 install_build_tools_for="BUILD HOST"
368 build_mangle="build_"
371 install_build_tools_for="BUILD HOST"
373 *) CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
377 # Save the real tuples to generate shell-wrappers to the real tools
378 CT_REAL_BUILD="${CT_BUILD}"
379 CT_REAL_HOST="${CT_HOST}"
380 CT_REAL_TARGET="${CT_TARGET}"
382 # Canonicalise CT_BUILD and CT_HOST
383 # Not only will it give us full-qualified tuples, but it will also ensure
384 # that they are valid tuples (in case of typo with user-provided tuples)
385 # That's way better than trying to rewrite config.sub ourselves...
386 # CT_TARGET is already made canonical in CT_DoBuildTargetTuple
387 CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
388 CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
390 # Modify BUILD and HOST so that gcc always generate a cross-compiler
391 # even if any of the build, host or target machines are the same.
392 # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
393 # support canadain build, later...
394 CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
395 CT_HOST="${CT_HOST/-/-${host_mangle}}"
396 CT_TARGET="${CT_TARGET/-/-${target_mangle}}"
398 # Now we have mangled our BUILD and HOST tuples, we must fake the new
399 # cross-tools for those mangled tuples.
400 CT_DoLog DEBUG "Making build system tools available"
401 for m in ${install_build_tools_for}; do
406 if [ -n "${!p}" ]; then
412 for tool in ar as dlltool gcc g++ gcj gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
413 # First try with prefix + suffix
414 # Then try with prefix only
415 # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
416 # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
417 # This is needed, because some tools have a prefix and
418 # a suffix (eg. gcc), while others may have only one,
419 # or even none (eg. binutils)
420 where=$(CT_Which "${t}${tool}${!s}")
421 [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
423 -a \( "${m}" = "BUILD" \
424 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
425 where=$(CT_Which "${tool}${!s}")
428 -a \( "${m}" = "BUILD" \
429 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
430 where=$(CT_Which "${tool}")
433 # Not all tools are available for all platforms, but some are really,
435 if [ -n "${where}" ]; then
436 CT_DoLog DEBUG " '${!v}-${tool}' -> '${where}'"
437 printf "#${BANG}${CT_CONFIG_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_BUILDTOOLS_PREFIX_DIR}/bin/${!v}-${tool}"
438 CT_DoExecLog ALL chmod 700 "${CT_BUILDTOOLS_PREFIX_DIR}/bin/${!v}-${tool}"
441 # We'll at least need some of them...
442 ar|as|gcc|ld|nm|objcopy|objdump|ranlib)
443 CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
445 # Some are conditionnally required
446 # Add them in alphabetical (C locale) ordering
448 # g++ (needed for companion lib), only needed for HOST
449 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${m}" = "HOST"
452 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_CC_LANG_JAVA}" = "y"
455 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_STRIP_ALL_TOOLCHAIN_EXECUTABLES}" = "y"
457 # If any other is missing, only warn at low level
459 # It does not deserve a WARN level.
460 CT_DoLog DEBUG " Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
467 # Some makeinfo versions are a pain in [put your most sensible body part here].
468 # Go ahead with those, by creating a wrapper that keeps partial files, and that
470 CT_DoLog DEBUG " 'makeinfo' -> '$(CT_Which makeinfo)'"
471 printf "#${BANG}${CT_CONFIG_SHELL}\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue\n" >"${CT_BUILDTOOLS_PREFIX_DIR}/bin/makeinfo"
472 CT_DoExecLog ALL chmod 700 "${CT_BUILDTOOLS_PREFIX_DIR}/bin/makeinfo"
474 # Carefully add paths in the order we want them:
475 # - first try in ${CT_PREFIX_DIR}/bin
476 # - then try the buildtools dir
477 # - fall back to searching user's PATH
478 # Of course, neither cross-native nor canadian can run on BUILD,
479 # so don't add those PATHs in this case...
480 case "${CT_TOOLCHAIN_TYPE}" in
481 cross) export PATH="${CT_PREFIX_DIR}/bin:${CT_BUILDTOOLS_PREFIX_DIR}/bin:${PATH}";;
482 canadian) export PATH="${CT_BUILDTOOLS_PREFIX_DIR}/bin:${PATH}";;
486 # Now we know our host and where to find the host tools, we can check
487 # if static link was requested, but only if it was requested
488 if [ "${CT_WANTS_STATIC_LINK}" = "y" ]; then
489 tmp="${CT_BUILD_DIR}/.static-test"
490 if ! "${CT_HOST}-gcc" -xc - -static -o "${tmp}" >/dev/null 2>&1 <<-_EOF_
491 int main() { return 0; }
494 CT_Abort "Static linking impossible on the host system '${CT_HOST}'"
501 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST+=" -pipe"
502 CT_CFLAGS_FOR_HOST+=" ${CT_EXTRA_FLAGS_FOR_HOST}"
504 # Set the shell to be used by ./configure scripts and by Makefiles (those
506 export CONFIG_SHELL="${CT_CONFIG_SHELL}" # for ./configure
507 export SHELL="${CT_CONFIG_SHELL}" # for Makefiles
509 # And help make go faster
511 # Override the configured jobs with what's been given on the command line
512 [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
513 # Use the number of processors+1 when automatically setting the number of
514 # parallel jobs. Fall back to 1 if the host doesn't use GLIBC.
515 AUTO_JOBS=$((`getconf _NPROCESSORS_ONLN 2> /dev/null || echo 0` + 1))
516 [ ${CT_PARALLEL_JOBS} -eq 0 ] && JOBSFLAGS="${JOBSFLAGS} -j${AUTO_JOBS}"
517 [ ${CT_PARALLEL_JOBS} -gt 0 ] && JOBSFLAGS="${JOBSFLAGS} -j${CT_PARALLEL_JOBS}"
518 [ ${CT_LOAD} -ne 0 ] && JOBSFLAGS="${JOBSFLAGS} -l${CT_LOAD}"
520 # We need to save the real .config with kconfig's value,
521 # not our mangled .config.2 with arrays.
522 CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
523 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/bin"
524 CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/scripts/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
525 CT_DoExecLog DEBUG sed -i -e 's,@@grep@@,"'"${grep}"'",;' "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
526 bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
528 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
529 CT_DoLog EXTRA "Building a toolchain for:"
530 CT_DoLog EXTRA " build = ${CT_REAL_BUILD}"
531 CT_DoLog EXTRA " host = ${CT_REAL_HOST}"
532 CT_DoLog EXTRA " target = ${CT_TARGET}"
533 set |grep -E '^CT_.+=' |sort |CT_DoLog DEBUG
534 CT_DoLog DEBUG "Other environment:"
535 printenv |grep -v -E '^CT_.+=' |CT_DoLog DEBUG
539 if [ -z "${CT_RESTART}" ]; then
540 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
541 do_companion_tools_get
558 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
559 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
560 CT_DoForceRmdir "${CT_SRC_DIR}"
561 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
564 if [ "${CT_COMP_TOOLS}" = "y" ]; then
565 CT_DoStep INFO "Extracting, patching and installing companion tools"
566 do_companion_tools_extract
571 CT_DoStep INFO "Extracting and patching toolchain components"
585 do_test_suite_extract
590 # Now for the job by itself. Go have a coffee!
591 if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
592 # Because of CT_RESTART, this becomes quite complex
595 [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
596 # Aha! CT_STEPS comes from steps.mk!
597 for step in ${CT_STEPS}; do
598 if [ ${do_it} -eq 0 ]; then
599 if [ "${CT_RESTART}" = "${step}" ]; then
600 CT_DoLoadState "${step}"
605 CT_DoSaveState ${step}
606 if [ ${do_stop} -eq 1 ]; then
607 CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
611 if [ ${do_it} -eq 1 ]; then
613 # POSIX 1003.1-2008 does not say if "set -e" should catch a
614 # sub-shell ending with !0. bash-3 does not, while bash-4 does,
615 # so the following line is for bash-3; bash-4 would choke above.
617 if [ "${CT_STOP}" = "${step}" ]; then
620 if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
621 CT_DoPause "Step '${step}' finished"
630 # From now-on, it can become impossible to log any time, because
631 # either we're compressing the log file, or it can become RO any
632 # moment... Consign all ouptut to oblivion...
633 CT_DoLog INFO "Finishing installation (may take a few seconds)..."
635 rm -f ${CT_PREFIX_DIR}/build.log.bz2
636 if [ "${CT_LOG_TO_FILE}" = "y" ]; then
637 cp "${tmp_log_file}" "${CT_PREFIX_DIR}/build.log"
638 if [ "${CT_LOG_FILE_COMPRESS}" = y ]; then
639 bzip2 -9 "${CT_PREFIX_DIR}/build.log"
642 [ "${CT_INSTALL_DIR_RO}" = "y" ] && chmod -R a-w "${CT_INSTALL_DIR}"
643 [ "${CT_TEST_SUITE}" = "y" ] && chmod -R u+w "${CT_TEST_SUITE_DIR}"