samples: add a new samples for the TI DaVinci processors.
Dragan Marinkovic <marinkovic.dragan@gmail.com> wrote:
I finally had the time (and board) to spend some time with
crosstool-NG version 1.5.2 and TMS320DM6446 (DaVinci Digital Media
System-on-Chip,
http://focus.ti.com/docs/prod/folders/print/tms320dm6446.html).
I was able to successfully build and run v2.6.27-davinci1 kernel
(Kevin Hilman's branch) with busybox based initramfs on it. I don't
believe that any later kernel would represent any challenge (it just
happens that I'm currently working with this version). What a thrill
:).
crosstool-NG/toolchain config is attached. It may be useful to someone
using crosstool-NG ...
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"
64 # Will be plain /bin/sh on most systems, except if we have /bin/ash and we
65 # _explictly_ required using it
66 case "${CT_CONFIG_SHELL}" in
67 sh) CT_SHELL="/bin/sh";;
68 ash) CT_SHELL="/bin/ash";;
69 bash) CT_SHELL="${BASH}";;
70 custom) CT_SHELL="${CT_CONFIG_SHELL_CUSTOM_PATH}";;
73 # Check the user is using an existing SHELL to be used by ./configure and Makefiles
74 CT_TestOrAbort "The CONFIG_SHELL '${CT_CONFIG_SHELL}' (${CT_SHELL}) is not valid" -f "${CT_SHELL}" -a -x "${CT_SHELL}"
76 # Create the bin-overide early
77 # Contains symlinks to the tools found by ./configure
78 # Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so
79 # they can be safely used
80 CT_BIN_OVERIDE_DIR="${CT_WORK_DIR}/bin"
81 CT_DoLog DEBUG "Creating bin-overide for tools in '${CT_BIN_OVERIDE_DIR}'"
82 CT_DoExecLog DEBUG mkdir -p "${CT_BIN_OVERIDE_DIR}"
83 cat "${CT_LIB_DIR}/paths.mk" |while read trash line; do
86 CT_DoLog DEBUG "Creating script-override for '${tool}' -> '${path}'"
87 printf "#${BANG}${CT_SHELL}\nexec '${path}' \"\${@}\"\n" >"${CT_BIN_OVERIDE_DIR}/${tool}"
88 CT_DoExecLog ALL chmod 700 "${CT_BIN_OVERIDE_DIR}/${tool}"
90 export PATH="${CT_BIN_OVERIDE_DIR}:${PATH}"
92 # Start date. Can't be done until we know the locale
93 # Also requires the bin-override tools
94 CT_STAR_DATE=$(CT_DoDate +%s%N)
95 CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
97 # Log real begining of build, now
98 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
101 CT_DoExecLog DEBUG renice ${CT_NICE} $$
103 CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
104 CT_DoExecLog DEBUG grep -E '^(# |)CT_' .config
107 CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
111 CT_DoLog INFO "Building environment variables"
113 # Include sub-scripts instead of calling them: that way, we do not have to
114 # export any variable, nor re-parse the configuration and functions files.
115 . "${CT_LIB_DIR}/scripts/build/internals.sh"
116 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
117 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
118 . "${CT_LIB_DIR}/scripts/build/companion_libs/gmp.sh"
119 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpfr.sh"
120 . "${CT_LIB_DIR}/scripts/build/companion_libs/ppl.sh"
121 . "${CT_LIB_DIR}/scripts/build/companion_libs/cloog.sh"
122 . "${CT_LIB_DIR}/scripts/build/companion_libs/mpc.sh"
123 . "${CT_LIB_DIR}/scripts/build/binutils/binutils.sh"
124 . "${CT_LIB_DIR}/scripts/build/binutils/elf2flt.sh"
125 . "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
126 . "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
127 . "${CT_LIB_DIR}/scripts/build/tools.sh"
128 . "${CT_LIB_DIR}/scripts/build/debug.sh"
130 # Target tuple: CT_TARGET needs a little love:
131 CT_DoBuildTargetTuple
133 # Kludge: If any of the configured options needs CT_TARGET,
134 # then rescan the options file now:
137 # Sanity check some directories
138 CT_TestAndAbort "'CT_PREFIX_DIR' is not set: where should I install?" -z "${CT_PREFIX_DIR}"
140 # Second kludge: merge user-supplied target CFLAGS with architecture-provided
141 # target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
142 # Put user-supplied flags at the end, so that they take precedence.
143 CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
144 CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
145 CT_CC_CORE_EXTRA_CONFIG="${CT_ARCH_CC_CORE_EXTRA_CONFIG} ${CT_CC_CORE_EXTRA_CONFIG}"
146 CT_CC_EXTRA_CONFIG="${CT_ARCH_CC_EXTRA_CONFIG} ${CT_CC_EXTRA_CONFIG}"
148 # Compute the working directories names
149 CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
150 CT_SRC_DIR="${CT_WORK_DIR}/src"
151 CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
152 CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
153 CT_CONFIG_DIR="${CT_BUILD_DIR}/configs"
155 # Note: we'll always install the core compiler in its own directory, so as to
156 # not mix the two builds: core and final.
157 CT_CC_CORE_STATIC_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-static"
158 CT_CC_CORE_SHARED_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-shared"
160 # Set LD_LIBRARY_PATH to point to prefix/lib so we can find our own
161 # libraries; add as first path, so we get hit first by the dynamic linker
162 CT_SetLibPath "${CT_PREFIX_DIR}/lib" first
164 # We must ensure that we can restart if asked for!
165 if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}" ]; then
166 CT_DoLog ERROR "You asked to restart a non-restartable build"
167 CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
168 CT_DoLog ERROR "in the config options for the previous build, or the state"
169 CT_DoLog ERROR "directory for the previous build was deleted."
170 CT_Abort "I will stop here to avoid any carnage"
173 # If the local tarball directory does not exist, say so, and don't try to save there!
174 if [ "${CT_SAVE_TARBALLS}" = "y" \
175 -a ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
176 CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist."
177 CT_DoLog WARN "Will not save downloaded tarballs to local storage."
181 # Check now if we can write to the destination directory:
182 if [ -d "${CT_INSTALL_DIR}" ]; then
183 CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
186 # Good, now grab a bit of informations on the system we're being run on,
187 # just in case something goes awok, and it's not our fault:
188 CT_SYS_USER=$(id -un)
189 CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
190 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
191 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
192 CT_SYS_KERNEL=$(uname -s)
193 CT_SYS_REVISION=$(uname -r)
194 # MacOS X lacks '-o' :
195 CT_SYS_OS=$(uname -o || echo "Unknown (maybe MacOS-X)")
196 CT_SYS_MACHINE=$(uname -m)
197 CT_SYS_PROCESSOR=$(uname -p)
198 CT_SYS_GCC=$(gcc -dumpversion)
199 CT_SYS_TARGET=$(CT_DoConfigGuess)
200 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
202 CT_DoLog EXTRA "Preparing working directories"
204 # Ah! The build directory shall be eradicated, even if we restart!
205 if [ -d "${CT_BUILD_DIR}" ]; then
206 CT_DoForceRmdir "${CT_BUILD_DIR}"
209 # Don't eradicate directories if we need to restart
210 if [ -z "${CT_RESTART}" ]; then
211 # Get rid of pre-existing installed toolchain and previous build directories.
212 # We need to do that _before_ we can safely log, because the log file will
213 # most probably be in the toolchain directory.
214 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
215 CT_DoForceRmdir "${CT_TARBALLS_DIR}"
217 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
218 CT_DoForceRmdir "${CT_SRC_DIR}"
220 if [ -d "${CT_INSTALL_DIR}" ]; then
221 CT_DoForceRmdir "${CT_INSTALL_DIR}"
223 # In case we start anew, get rid of the previously saved state directory
224 if [ -d "${CT_STATE_DIR}" ]; then
225 CT_DoForceRmdir "${CT_STATE_DIR}"
229 # Create the directories we'll use, even if restarting: it does no harm to
230 # create already existent directories, and CT_BUILD_DIR needs to be created
232 CT_DoExecLog ALL mkdir -p "${CT_TARBALLS_DIR}"
233 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
234 CT_DoExecLog ALL mkdir -p "${CT_BUILD_DIR}"
235 CT_DoExecLog ALL mkdir -p "${CT_CONFIG_DIR}"
236 CT_DoExecLog ALL mkdir -p "${CT_INSTALL_DIR}"
237 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}"
238 if [ -z "${CT_CANADIAN}" ]; then
239 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_STATIC_PREFIX_DIR}"
240 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_SHARED_PREFIX_DIR}"
243 # Only create the state dir if asked for a restartable build
244 [ -n "${CT_DEBUG_CT_SAVE_STEPS}" ] && CT_DoExecLog ALL mkdir -p "${CT_STATE_DIR}"
246 # Check install file system case-sensitiveness
247 CT_DoExecLog DEBUG touch "${CT_PREFIX_DIR}/foo"
248 CT_TestAndAbort "Your file system in '${CT_PREFIX_DIR}' is *not* case-sensitive!" -f "${CT_PREFIX_DIR}/FOO"
249 CT_DoExecLog DEBUG rm -f "${CT_PREFIX_DIR}/foo"
251 # Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
252 # the previous build was successful. To be able to move the logfile there,
253 # switch them back to read/write
254 CT_DoExecLog ALL chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
256 # Redirect log to the actual log file now we can
257 # It's quite understandable that the log file will be installed in the install
258 # directory, so we must first ensure it exists and is writeable (above) before
261 case "${CT_LOG_TO_FILE}" in
262 y) CT_LOG_FILE="${CT_PREFIX_DIR}/build.log"
263 cat "${tmp_log_file}" >>"${CT_LOG_FILE}"
264 rm -f "${tmp_log_file}"
265 exec >>"${CT_LOG_FILE}"
267 *) rm -f "${tmp_log_file}"
271 # Setting up the rest of the environment only if not restarting
272 if [ -z "${CT_RESTART}" ]; then
273 # Arrange paths depending on wether we use sys-root or not.
274 if [ "${CT_USE_SYSROOT}" = "y" ]; then
275 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root"
276 CT_DEBUGROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/debug-root"
277 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
278 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
279 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
280 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
282 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
283 # confused when $sysroot/usr/include is not present.
284 # Note: --prefix=/usr is magic!
285 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
287 # plain old way. All libraries in prefix/target/lib
288 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
289 CT_DEBUGROOT_DIR="${CT_SYSROOT_DIR}"
290 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
291 # hack! Always use --with-sysroot for binutils.
292 # binutils 2.14 and later obey it, older binutils ignore it.
293 # Lets you build a working 32->64 bit cross gcc
294 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
295 # Use --with-headers, else final gcc will define disable_glibc while
296 # building libgcc, and you'll have no profiling
297 CC_CORE_SYSROOT_ARG="--without-headers"
298 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
299 LIBC_SYSROOT_ARG="prefix="
301 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}"
302 CT_DoExecLog ALL mkdir -p "${CT_DEBUGROOT_DIR}"
304 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
305 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail
306 # with: "ld: cannot open crti.o: No such file or directory"
307 # Also prepare the lib directory in the install dir, else some 64 bit archs
309 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/lib"
310 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/lib"
311 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
313 if [ "${CT_USE_SYSROOT}" = "y" ]; then
314 # Prevent gcc from installing its libraries outside of the sys-root
315 CT_DoExecLog ALL ln -sf "./${CT_SYSROOT_DIR_PREFIX}/sys-root/lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib"
318 # Now, in case we're 64 bits, just have lib64/ be a symlink to lib/
319 # so as to have all libraries in the same directory (we can do that
320 # because we are *not* multilib).
321 if [ "${CT_ARCH_64}" = "y" ]; then
322 CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/lib64"
323 CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/lib64"
324 CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/usr/lib64"
325 CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib64"
328 # Determine build system if not set by the user
329 CT_Test "You did not specify the build system. That's OK, I can guess..." -z "${CT_BUILD}"
330 case "${CT_BUILD}" in
331 "") CT_BUILD=$("${CT_BUILD_PREFIX}gcc${CT_BUILD_SUFFIX}" -dumpmachine);;
334 # Prepare mangling patterns to later modify BUILD and HOST (see below)
335 case "${CT_TOOLCHAIN_TYPE}" in
337 # A cross-compiler runs on the same machine it is built on
338 CT_HOST="${CT_BUILD}"
339 build_mangle="build_"
342 install_build_tools_for="BUILD HOST"
345 build_mangle="build_"
348 install_build_tools_for="BUILD HOST TARGET"
350 *) CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
354 # Save the real tuples to generate shell-wrappers to the real tools
355 CT_REAL_BUILD="${CT_BUILD}"
356 CT_REAL_HOST="${CT_HOST}"
357 CT_REAL_TARGET="${CT_TARGET}"
359 # Canonicalise CT_BUILD and CT_HOST
360 # Not only will it give us full-qualified tuples, but it will also ensure
361 # that they are valid tuples (in case of typo with user-provided tuples)
362 # That's way better than trying to rewrite config.sub ourselves...
363 # CT_TARGET is already made canonical in CT_DoBuildTargetTuple
364 CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
365 CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
367 # Modify BUILD and HOST so that gcc always generate a cross-compiler
368 # even if any of the build, host or target machines are the same.
369 # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
370 # support canadain build, later...
371 CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
372 CT_HOST="${CT_HOST/-/-${host_mangle}}"
373 CT_TARGET="${CT_TARGET/-/-${target_mangle}}"
375 # Now we have mangled our BUILD and HOST tuples, we must fake the new
376 # cross-tools for those mangled tuples.
377 CT_DoLog DEBUG "Making build system tools available"
378 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/buildtools"
379 for m in ${install_build_tools_for}; do
384 if [ -n "${!p}" ]; then
390 for tool in ar as dlltool gcc g++ gcj gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
391 # First try with prefix + suffix
392 # Then try with prefix only
393 # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
394 # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
395 # This is needed, because some tools have a prefix and
396 # a suffix (eg. gcc), while others may have only one,
397 # or even none (eg. binutils)
398 where=$(CT_Which "${t}${tool}${!s}")
399 [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
401 -a \( "${m}" = "BUILD" \
402 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
403 where=$(CT_Which "${tool}${!s}")
406 -a \( "${m}" = "BUILD" \
407 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
408 where=$(CT_Which "${tool}")
411 # Not all tools are available for all platforms, but some are really,
413 if [ -n "${where}" ]; then
414 CT_DoLog DEBUG " '${!v}-${tool}' -> '${where}'"
415 printf "#${BANG}${CT_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_PREFIX_DIR}/buildtools/${!v}-${tool}"
416 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/buildtools/${!v}-${tool}"
419 # We'll at least need some of them...
420 ar|as|gcc|g++|ld|nm|objcopy|objdump|ranlib)
421 CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
423 # Some are conditionnally required
424 # Add them in alphabetical (C locale) ordering
426 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_CC_LANG_JAVA}" = "y"
428 # If any other is missing, only warn at low level
430 # It does not deserve a WARN level.
431 CT_DoLog DEBUG " Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
438 # Carefully add paths in the order we want them:
439 # - first try in ${CT_PREFIX_DIR}/bin
440 # - then try in ${CT_CC_CORE_SHARED_PREFIX_DIR}/bin
441 # - then try in ${CT_CC_CORE_STATIC_PREFIX_DIR}/bin
442 # - fall back to searching user's PATH
443 # Of course, neither cross-native nor canadian can run on BUILD,
444 # so don't add those PATHs in this case...
445 case "${CT_TOOLCHAIN_TYPE}" in
446 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}";;
447 canadian) export PATH="${CT_PREFIX_DIR}/buildtools:${PATH}";;
451 # Some makeinfo versions are a pain in [put your most sensible body part here].
452 # Go ahead with those, by creating a wrapper that keeps partial files, and that
454 CT_DoLog DEBUG " 'makeinfo' -> '$(CT_Which makeinfo)'"
455 printf "#${BANG}${CT_SHELL}\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue\n" >"${CT_PREFIX_DIR}/buildtools/makeinfo"
456 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/buildtools/makeinfo"
460 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
462 # Override the configured jobs with what's been given on the command line
463 [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
465 # Set the shell to be used by ./configure scripts and by Makefiles (those
467 export CONFIG_SHELL="${CT_SHELL}" # for ./configure
468 export SHELL="${CT_SHELL}" # for Makefiles
470 # And help make go faster
472 [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
473 [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
474 export PARALLELMFLAGS
476 CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
477 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/bin"
478 CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/scripts/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
479 CT_DoExecLog DEBUG sed -r -i -e 's,@@grep@@,"'"${grep}"'",;' "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
480 bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
482 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
483 CT_DoLog EXTRA "Building a toolchain for:"
484 CT_DoLog EXTRA " build = ${CT_REAL_BUILD}"
485 CT_DoLog EXTRA " host = ${CT_REAL_HOST}"
486 CT_DoLog EXTRA " target = ${CT_TARGET}"
487 set |grep -E '^CT_.+=' |sort |CT_DoLog DEBUG
491 if [ -z "${CT_RESTART}" ]; then
492 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
506 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
507 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
508 CT_DoForceRmdir "${CT_SRC_DIR}"
509 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
511 CT_DoStep INFO "Extracting and patching toolchain components"
527 # Now for the job by itself. Go have a coffee!
528 if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
529 # Because of CT_RESTART, this becomes quite complex
532 [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
533 # Aha! CT_STEPS comes from steps.mk!
534 for step in ${CT_STEPS}; do
535 if [ ${do_it} -eq 0 ]; then
536 if [ "${CT_RESTART}" = "${step}" ]; then
537 CT_DoLoadState "${step}"
542 CT_DoSaveState ${step}
543 if [ ${do_stop} -eq 1 ]; then
544 CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
548 if [ ${do_it} -eq 1 ]; then
550 if [ "${CT_STOP}" = "${step}" ]; then
553 if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
554 CT_DoPause "Step '${step}' finished"
563 # From now-on, it can become impossible to log any time, because
564 # either we're compressing the log file, or it can become RO any
565 # moment... Consign all ouptut to oblivion...
566 CT_DoLog INFO "Finishing installation (may take a few seconds)..."
569 [ "${CT_LOG_FILE_COMPRESS}" = y ] && bzip2 -9 "${CT_LOG_FILE}"
570 [ "${CT_INSTALL_DIR_RO}" = "y" ] && chmod -R a-w "${CT_INSTALL_DIR}"