Allow user to add a directory component in the sys-root path.
Rename CT_DEBUG_INSTALL_DIR to CT_DEBUGROOT_DIR (to match CT_SYSROOT_DIR).
As a side effect, fix creating lib64->lib symlinks.
/trunk/scripts/build/debug/100-dmalloc.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/400-ltrace.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/300-gdb.sh | 6 3 3 0 +++---
/trunk/scripts/build/debug/500-strace.sh | 2 1 1 0 +-
/trunk/scripts/build/debug/200-duma.sh | 6 3 3 0 +++---
/trunk/scripts/crosstool-NG.sh.in | 16 7 9 0 +++++++---------
/trunk/scripts/functions | 2 1 1 0 +-
/trunk/config/toolchain.in | 17 17 0 0 +++++++++++++++++
8 files changed, 34 insertions(+), 19 deletions(-)
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
32 CT_WORK_DIR="${CT_WORK_DIR:-${CT_TOP_DIR}/targets}"
34 # Create the bin-overide early
35 # Contains symlinks to the tools found by ./configure
36 # Note: CT_DoLog and CT_DoExecLog do not use any of those tool, so
37 # they can be safely used
38 CT_BIN_OVERIDE_DIR="${CT_WORK_DIR}/bin"
39 CT_DoLog DEBUG "Creating bin-overide for tools in '${CT_BIN_OVERIDE_DIR}'"
40 CT_DoExecLog DEBUG mkdir -p "${CT_BIN_OVERIDE_DIR}"
41 cat "${CT_LIB_DIR}/paths.mk" |while read trash line; do
44 CT_DoLog DEBUG " '${tool}' -> '${path}'"
45 printf "#${BANG}/bin/sh\nexec '${path}' \"\${@}\"\n" >"${CT_BIN_OVERIDE_DIR}/${tool}"
46 CT_DoExecLog ALL chmod 700 "${CT_BIN_OVERIDE_DIR}/${tool}"
48 export PATH="${CT_BIN_OVERIDE_DIR}:${PATH}"
50 # Start date. Can't be done until we know the locale
51 CT_STAR_DATE=$(CT_DoDate +%s%N)
52 CT_STAR_DATE_HUMAN=$(CT_DoDate +%Y%m%d.%H%M%S)
54 # Log real begining of build, now
55 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
58 CT_DoExecLog DEBUG renice ${CT_NICE} $$
60 CT_DoStep DEBUG "Dumping user-supplied crosstool-NG configuration"
61 CT_DoExecLog DEBUG egrep '^(# |)CT_' .config
64 # Some sanity checks in the environment and needed tools
65 CT_DoLog INFO "Checking environment sanity"
67 CT_DoLog DEBUG "Unsetting and unexporting MAKEFLAGS"
71 # Other environment sanity checks
72 CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
73 CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
74 CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
75 CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
78 CT_DoLog INFO "Building environment variables"
80 # Include sub-scripts instead of calling them: that way, we do not have to
81 # export any variable, nor re-parse the configuration and functions files.
82 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"
83 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"
84 . "${CT_LIB_DIR}/scripts/build/gmp.sh"
85 . "${CT_LIB_DIR}/scripts/build/mpfr.sh"
86 . "${CT_LIB_DIR}/scripts/build/binutils.sh"
87 . "${CT_LIB_DIR}/scripts/build/libc/${CT_LIBC}.sh"
88 . "${CT_LIB_DIR}/scripts/build/cc/${CT_CC}.sh"
89 . "${CT_LIB_DIR}/scripts/build/tools.sh"
90 . "${CT_LIB_DIR}/scripts/build/debug.sh"
92 # Target tuple: CT_TARGET needs a little love:
95 # Kludge: If any of the configured options needs CT_TARGET,
96 # then rescan the options file now:
99 # Second kludge: merge user-supplied target CFLAGS with architecture-provided
100 # target CFLAGS. Do the same for LDFLAGS in case it happens in the future.
101 # Put user-supplied flags at the end, so that they take precedence.
102 CT_TARGET_CFLAGS="${CT_ARCH_TARGET_CFLAGS} ${CT_TARGET_CFLAGS}"
103 CT_TARGET_LDFLAGS="${CT_ARCH_TARGET_LDFLAGS} ${CT_TARGET_LDFLAGS}"
104 CT_CC_CORE_EXTRA_CONFIG="${CT_ARCH_CC_CORE_EXTRA_CONFIG} ${CT_CC_CORE_EXTRA_CONFIG}"
105 CT_CC_EXTRA_CONFIG="${CT_ARCH_CC_EXTRA_CONFIG} ${CT_CC_EXTRA_CONFIG}"
107 # Create the working directories
108 CT_TARBALLS_DIR="${CT_WORK_DIR}/tarballs"
109 CT_SRC_DIR="${CT_WORK_DIR}/src"
110 CT_BUILD_DIR="${CT_WORK_DIR}/${CT_TARGET}/build"
111 # Note: we'll always install the core compiler in its own directory, so as to
112 # not mix the two builds: core and final.
113 CT_CC_CORE_STATIC_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-static"
114 CT_CC_CORE_SHARED_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-shared"
115 CT_STATE_DIR="${CT_WORK_DIR}/${CT_TARGET}/state"
117 # We must ensure that we can restart if asked for!
118 if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}" ]; then
119 CT_DoLog ERROR "You asked to restart a non-restartable build"
120 CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
121 CT_DoLog ERROR "in the config options for the previous build, or the state"
122 CT_DoLog ERROR "directory for the previous build was deleted."
123 CT_Abort "I will stop here to avoid any carnage"
126 # If the local tarball directory does not exist, say so, and don't try to save there!
127 if [ ! -d "${CT_LOCAL_TARBALLS_DIR}" ]; then
128 CT_DoLog WARN "Directory '${CT_LOCAL_TARBALLS_DIR}' does not exist. Will not save downloaded tarballs to local storage."
132 # Some more sanity checks now that we have all paths set up
133 case "${CT_LOCAL_TARBALLS_DIR},${CT_TARBALLS_DIR},${CT_SRC_DIR},${CT_BUILD_DIR},${CT_PREFIX_DIR},${CT_INSTALL_DIR}" in
134 *" "*) CT_Abort "Don't use spaces in paths, it breaks things.";;
137 # Check now if we can write to the destination directory:
138 if [ -d "${CT_INSTALL_DIR}" ]; then
139 CT_TestAndAbort "Destination directory '${CT_INSTALL_DIR}' is not removable" ! -w $(dirname "${CT_INSTALL_DIR}")
142 # Good, now grab a bit of informations on the system we're being run on,
143 # just in case something goes awok, and it's not our fault:
144 CT_SYS_USER=$(id -un)
145 CT_SYS_HOSTNAME=$(hostname -f 2>/dev/null || true)
146 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
147 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-$(uname -n)}"
148 CT_SYS_KERNEL=$(uname -s)
149 CT_SYS_REVISION=$(uname -r)
150 # MacOS X lacks '-o' :
151 CT_SYS_OS=$(uname -o || echo "Unknown (maybe MacOS-X)")
152 CT_SYS_MACHINE=$(uname -m)
153 CT_SYS_PROCESSOR=$(uname -p)
154 CT_SYS_GCC=$(gcc -dumpversion)
155 CT_SYS_TARGET=$(CT_DoConfigGuess)
156 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
158 CT_DoLog EXTRA "Preparing working directories"
160 # Ah! The build directory shall be eradicated, even if we restart!
161 if [ -d "${CT_BUILD_DIR}" ]; then
162 CT_DoForceRmdir "${CT_BUILD_DIR}"
165 # Don't eradicate directories if we need to restart
166 if [ -z "${CT_RESTART}" ]; then
167 # Get rid of pre-existing installed toolchain and previous build directories.
168 # We need to do that _before_ we can safely log, because the log file will
169 # most probably be in the toolchain directory.
170 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
171 CT_DoForceRmdir "${CT_TARBALLS_DIR}"
173 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
174 CT_DoForceRmdir "${CT_SRC_DIR}"
176 if [ -d "${CT_INSTALL_DIR}" ]; then
177 CT_DoForceRmdir "${CT_INSTALL_DIR}"
179 # In case we start anew, get rid of the previously saved state directory
180 if [ -d "${CT_STATE_DIR}" ]; then
181 CT_DoForceRmdir "${CT_STATE_DIR}"
185 # Create the directories we'll use, even if restarting: it does no harm to
186 # create already existent directories, and CT_BUILD_DIR needs to be created
188 CT_DoExecLog ALL mkdir -p "${CT_TARBALLS_DIR}"
189 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
190 CT_DoExecLog ALL mkdir -p "${CT_BUILD_DIR}"
191 CT_DoExecLog ALL mkdir -p "${CT_INSTALL_DIR}"
192 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}"
193 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_STATIC_PREFIX_DIR}"
194 CT_DoExecLog ALL mkdir -p "${CT_CC_CORE_SHARED_PREFIX_DIR}"
195 CT_DoExecLog ALL mkdir -p "${CT_STATE_DIR}"
197 # Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
198 # the previous build was successful. To be able to move the logfile there,
199 # switch them back to read/write
200 CT_DoExecLog ALL chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
202 # Redirect log to the actual log file now we can
203 # It's quite understandable that the log file will be installed in the install
204 # directory, so we must first ensure it exists and is writeable (above) before
207 case "${CT_LOG_TO_FILE}" in
208 y) CT_LOG_FILE="${CT_PREFIX_DIR}/build.log"
209 cat "${tmp_log_file}" >>"${CT_LOG_FILE}"
210 rm -f "${tmp_log_file}"
211 exec >>"${CT_LOG_FILE}"
213 *) rm -f "${tmp_log_file}"
217 # Setting up the rest of the environment only if not restarting
218 if [ -z "${CT_RESTART}" ]; then
220 # Will be plain /bin/sh on most systems, except if we have /bin/ash and we
221 # _explictly_ required using it
223 [ "${CT_CONFIG_SHELL_ASH}" = "y" -a -x "/bin/ash" ] && CT_SHELL="/bin/ash"
225 # Arrange paths depending on wether we use sys-root or not.
226 if [ "${CT_USE_SYSROOT}" = "y" ]; then
227 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/sys-root"
228 CT_DEBUGROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/${CT_SYSROOT_DIR_PREFIX}/debug-root"
229 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
230 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
231 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
232 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
234 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
235 # confused when $sysroot/usr/include is not present.
236 # Note: --prefix=/usr is magic!
237 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
239 # plain old way. All libraries in prefix/target/lib
240 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
241 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
242 # hack! Always use --with-sysroot for binutils.
243 # binutils 2.14 and later obey it, older binutils ignore it.
244 # Lets you build a working 32->64 bit cross gcc
245 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
246 # Use --with-headers, else final gcc will define disable_glibc while
247 # building libgcc, and you'll have no profiling
248 CC_CORE_SYSROOT_ARG="--without-headers"
249 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
250 LIBC_SYSROOT_ARG="prefix="
252 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}"
253 CT_DoExecLog ALL mkdir -p "${CT_DEBUGROOT_DIR}"
255 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
256 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail
257 # with: "ld: cannot open crti.o: No such file or directory"
258 # Also prepare the lib directory in the install dir, else some 64 bit archs
260 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/lib"
261 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/lib"
262 CT_DoExecLog ALL mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
264 # Prevent gcc from installing its libraries outside of the sys-root
265 CT_DoExecLog ALL ln -sf "./${CT_SYSROOT_DIR_PREFIX}/sys-root/lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib"
267 # Now, in case we're 64 bits, just have lib64/ be a symlink to lib/
268 # so as to have all libraries in the same directory (we can do that
269 # because we are *not* multilib).
270 if [ "${CT_ARCH_64}" = "y" ]; then
271 CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/lib64"
272 CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/lib64"
273 CT_DoExecLog ALL ln -sf "lib" "${CT_SYSROOT_DIR}/usr/lib64"
274 CT_DoExecLog ALL ln -sf "lib" "${CT_PREFIX_DIR}/${CT_TARGET}/lib64"
277 # Determine build system if not set by the user
278 CT_Test "You did not specify the build system. That's OK, I can guess..." -z "${CT_BUILD}"
279 case "${CT_BUILD}" in
280 "") CT_BUILD=$("${CT_BUILD_PREFIX}gcc${CT_BUILD_SUFFIX}" -dumpmachine);;
283 # Prepare mangling patterns to later modify BUILD and HOST (see below)
284 case "${CT_TOOLCHAIN_TYPE}" in
286 CT_HOST="${CT_BUILD}"
287 build_mangle="build_"
290 *) CT_Abort "No code for '${CT_TOOLCHAIN_TYPE}' toolchain type!"
294 # Save the real tuples to generate shell-wrappers to the real tools
295 CT_REAL_BUILD="${CT_BUILD}"
296 CT_REAL_HOST="${CT_HOST}"
298 # Canonicalise CT_BUILD and CT_HOST
299 # Not only will it give us full-qualified tuples, but it will also ensure
300 # that they are valid tuples (in case of typo with user-provided tuples)
301 # That's way better than trying to rewrite config.sub ourselves...
302 CT_BUILD=$(CT_DoConfigSub "${CT_BUILD}")
303 CT_HOST=$(CT_DoConfigSub "${CT_HOST}")
305 # Modify BUILD and HOST so that gcc always generate a cross-compiler
306 # even if any of the build, host or target machines are the same.
307 # NOTE: we'll have to mangle the (BUILD|HOST)->TARGET x-compiler to
308 # support canadain build, later...
309 CT_BUILD="${CT_BUILD/-/-${build_mangle}}"
310 CT_HOST="${CT_HOST/-/-${host_mangle}}"
312 # Now we have mangled our BUILD and HOST tuples, we must fake the new
313 # cross-tools for those mangled tuples.
314 CT_DoLog DEBUG "Making build system tools available"
315 CT_DoExecLog ALL mkdir -p "${CT_PREFIX_DIR}/bin"
316 for m in BUILD HOST; do
321 if [ -n "${!p}" ]; then
327 for tool in ar as dlltool gcc g++ gcj gnatbind gnatmake ld nm objcopy objdump ranlib strip windres; do
328 # First try with prefix + suffix
329 # Then try with prefix only
330 # Then try with suffix only, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
331 # Finally try with neither prefix nor suffix, but only for BUILD, and HOST iff REAL_BUILD == REAL_HOST
332 # This is needed, because some tools have a prefix and
333 # a suffix (eg. gcc), while others may have only one,
334 # or even none (eg. binutils)
335 where=$(CT_Which "${t}${tool}${!s}")
336 [ -z "${where}" ] && where=$(CT_Which "${t}${tool}")
338 -a \( "${m}" = "BUILD" \
339 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
340 where=$(CT_Which "${tool}${!s}")
343 -a \( "${m}" = "BUILD" \
344 -o "${CT_REAL_BUILD}" = "${!r}" \) ]; then
345 where=$(CT_Which "${tool}")
348 # Not all tools are available for all platforms, but some are really,
350 if [ -n "${where}" ]; then
351 CT_DoLog DEBUG " '${!v}-${tool}' -> '${where}'"
352 printf "#${BANG}${CT_SHELL}\nexec '${where}' \"\${@}\"\n" >"${CT_PREFIX_DIR}/bin/${!v}-${tool}"
353 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/bin/${!v}-${tool}"
356 # We'll at least need some of them...
357 ar|as|gcc|ld|nm|objcopy|objdump|ranlib)
358 CT_Abort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!"
360 # Some are conditionnally required
361 # Add them in alphabetical (C locale) ordering
363 CT_TestAndAbort "Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : either needed!" "${CT_CC_LANG_JAVA}" = "y"
365 # If any other is missing, only warn at low level
367 # It does not deserve a WARN level.
368 CT_DoLog DEBUG " Missing: '${t}${tool}${!s}' or '${t}${tool}' or '${tool}' : not required."
375 # Carefully add paths in the order we want them:
376 # - first try in ${CT_PREFIX_DIR}/bin
377 # - then try in ${CT_CC_CORE_SHARED_PREFIX_DIR}/bin
378 # - then try in ${CT_CC_CORE_STATIC_PREFIX_DIR}/bin
379 # - fall back to searching user's PATH
380 # Of course, neither cross-native nor canadian can run on BUILD,
381 # so don't add those PATHs in this case...
382 case "${CT_TOOLCHAIN_TYPE}" in
383 cross) export PATH="${CT_PREFIX_DIR}/bin:${CT_CC_CORE_SHARED_PREFIX_DIR}/bin:${CT_CC_CORE_STATIC_PREFIX_DIR}/bin:${PATH}";;
387 # Some makeinfo versions are a pain in [put your most sensible body part here].
388 # Go ahead with those, by creating a wrapper that keeps partial files, and that
390 CT_DoLog DEBUG " 'makeinfo' -> '$(CT_Which makeinfo)'"
391 printf "#${BANG}/bin/sh\n$(CT_Which makeinfo) --force \"\${@}\"\ntrue\n" >"${CT_PREFIX_DIR}/bin/makeinfo"
392 CT_DoExecLog ALL chmod 700 "${CT_PREFIX_DIR}/bin/makeinfo"
396 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
398 # Override the configured jobs with what's been given on the command line
399 [ -n "${CT_JOBS}" ] && CT_PARALLEL_JOBS="${CT_JOBS}"
401 # Set the shell to be used by ./configure scripts and by Makefiles (those
403 export CONFIG_SHELL="${CT_SHELL}"
405 # And help make go faster
407 [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
408 [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
409 export PARALLELMFLAGS
411 CT_DoLog EXTRA "Installing user-supplied crosstool-NG configuration"
412 CT_DoExecLog DEBUG install -m 0755 "${CT_LIB_DIR}/scripts/toolchain-config.in" "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
413 CT_DoExecLog DEBUG sed -r -i -e 's,@@grep@@,"'"${grep}"'",;' "${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
414 bzip2 -c -9 .config >>"${CT_PREFIX_DIR}/bin/${CT_TARGET}-ct-ng.config"
416 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
417 CT_DoLog EXTRA "Building a toolchain for:"
418 CT_DoLog EXTRA " build = ${CT_REAL_BUILD}"
419 CT_DoLog EXTRA " host = ${CT_REAL_HOST}"
420 CT_DoLog EXTRA " target = ${CT_TARGET}"
421 set |egrep '^CT_.+=' |sort |CT_DoLog DEBUG
425 if [ -z "${CT_RESTART}" ]; then
426 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
437 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
438 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
439 CT_DoForceRmdir "${CT_SRC_DIR}"
440 CT_DoExecLog ALL mkdir -p "${CT_SRC_DIR}"
442 CT_DoStep INFO "Extracting and patching toolchain components"
455 # Now for the job by itself. Go have a coffee!
456 if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
457 # Because of CT_RESTART, this becomes quite complex
460 [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
461 # Aha! CT_STEPS comes from steps.mk!
462 for step in ${CT_STEPS}; do
463 if [ ${do_it} -eq 0 ]; then
464 if [ "${CT_RESTART}" = "${step}" ]; then
465 CT_DoLoadState "${step}"
470 CT_DoSaveState ${step}
471 if [ ${do_stop} -eq 1 ]; then
472 CT_DoLog ERROR "Stopping just after step '${prev_step}', as requested."
476 if [ ${do_it} -eq 1 ]; then
478 if [ "${CT_STOP}" = "${step}" ]; then
481 if [ "${CT_DEBUG_PAUSE_STEPS}" = "y" ]; then
482 CT_DoPause "Step '${step}' finished"
491 # From now-on, it can become impossible to log any time, because
492 # either we're compressing the log file, or it can become RO any
493 # moment... Consign all ouptut to oblivion...
494 CT_DoLog INFO "Finishing installation (may take a few seconds)..."
497 [ "${CT_LOG_FILE_COMPRESS}" = y ] && bzip2 -9 "${CT_LOG_FILE}"
498 [ "${CT_INSTALL_DIR_RO}" = "y" ] && chmod -R a-w "${CT_INSTALL_DIR}"