Don't go menuconfig if no .config present.
Handle the case where targets does not exist when calling distclean.
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 # CT_TOP_DIR is set by the makefile. If we don't have it, something's gone horribly wrong...
16 if [ -z "${CT_TOP_DIR}" -o ! -d "${CT_TOP_DIR}" ]; then
17 # We don't have the functions right now, because we don't have CT_TOP_DIR.
18 # Do the print stuff by hand:
19 echo "CT_TOP_DIR not set, or not a directory. Something's gone horribly wrong."
20 echo "Please send a bug report (see README)"
24 # Parse the common functions
25 . "${CT_TOP_DIR}/scripts/functions"
27 CT_STAR_DATE=`CT_DoDate +%s%N`
28 CT_STAR_DATE_HUMAN=`CT_DoDate +%Y%m%d.%H%M%S`
31 # - first of all, save stdout so we can see the live logs: fd #6
33 # - then point stdout to the log file (temporary for now)
34 tmp_log_file="${CT_TOP_DIR}/log.$$"
35 exec >>"${tmp_log_file}"
37 # Are we configured? We'll need that later...
38 CT_TestOrAbort "Configuration file not found. Please create one." -f "${CT_TOP_DIR}/.config"
40 # Parse the configuration file
41 # It has some info about the logging facility, so include it early
42 . "${CT_TOP_DIR}/.config"
45 renice ${CT_NICE} $$ |CT_DoLog DEBUG
47 # Yes! We can do full logging from now on!
48 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
50 CT_DoStep DEBUG "Dumping crosstool-NG configuration"
51 cat ${CT_TOP_DIR}/.config |egrep '^(# |)CT_' |CT_DoLog DEBUG
54 # Some sanity checks in the environment and needed tools
55 CT_DoLog INFO "Checking environment sanity"
57 # Enable known ordering of files in directory listings:
58 CT_Test "Crosstool-NG might not work as expected with LANG=\"${LANG}\"" -n "${LANG}"
59 case "${LC_COLLATE},${LC_ALL}" in
60 # These four combinations are known to sort files in the correct order:
65 # Anything else is destined to be borked if not gracefuly handled:
66 *) CT_DoLog WARN "Either LC_COLLATE=\"${LC_COLLATE}\" or LC_ALL=\"${LC_ALL}\" is not supported."
67 export LC_ALL=`locale -a |egrep "^(fr_FR|en_US)" |head -n 1`
68 CT_TestOrAbort "Neither en_US* nor fr_FR* locales found on your system." -n "${LC_ALL}"
69 CT_DoLog WARN "Forcing to known working LC_ALL=\"${LC_ALL}\"."
73 # Other environment sanity checks
74 CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
75 CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
76 CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
77 CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
84 CT_DoLog INFO "Building environment variables"
86 # Target triplet: CT_TARGET needs a little love:
87 CT_DoBuildTargetTriplet
89 # Kludge: If any of the configured options needs CT_TARGET,
90 # then rescan the options file now:
91 . "${CT_TOP_DIR}/.config"
93 # Now, build up the variables from the user-configured options.
94 CT_KERNEL_FILE="${CT_KERNEL}-${CT_KERNEL_VERSION}"
95 CT_BINUTILS_FILE="binutils-${CT_BINUTILS_VERSION}"
96 if [ "${CT_CC_USE_CORE}" != "y" ]; then
98 CT_CC_CORE_VERSION="${CT_CC_VERSION}"
99 CT_CC_CORE_EXTRA_CONFIG="${CT_CC_EXTRA_CONFIG}"
101 CT_CC_CORE_FILE="${CT_CC_CORE}-${CT_CC_CORE_VERSION}"
102 CT_CC_FILE="${CT_CC}-${CT_CC_VERSION}"
103 CT_LIBC_FILE="${CT_LIBC}-${CT_LIBC_VERSION}"
104 CT_LIBFLOAT_FILE="libfloat-${CT_LIBFLOAT_VERSION}"
106 # Where will we work?
107 CT_TARBALLS_DIR="${CT_TOP_DIR}/targets/tarballs"
108 CT_SRC_DIR="${CT_TOP_DIR}/targets/src"
109 CT_BUILD_DIR="${CT_TOP_DIR}/targets/${CT_TARGET}/build"
110 CT_DEBUG_INSTALL_DIR="${CT_INSTALL_DIR}/${CT_TARGET}/debug-root"
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. Anyway, its generic, wether we use
113 # a different compiler as core, or not.
114 CT_CC_CORE_STATIC_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-static"
115 CT_CC_CORE_SHARED_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core-shared"
116 CT_STATE_DIR="${CT_TOP_DIR}/targets/${CT_TARGET}/state"
118 # We must ensure that we can restart if asked for!
119 if [ -n "${CT_RESTART}" -a ! -d "${CT_STATE_DIR}" ]; then
120 CT_DoLog ERROR "You asked to restart a non-restartable build"
121 CT_DoLog ERROR "This happened because you didn't set CT_DEBUG_CT_SAVE_STEPS"
122 CT_DoLog ERROR "in the config options for the previous build, or the state"
123 CT_DoLog ERROR "directoy for the previous build was deleted."
124 CT_Abort "I will stop here to avoid any carnage"
127 # Make all path absolute, it so much easier!
128 CT_LOCAL_TARBALLS_DIR="`CT_MakeAbsolutePath \"${CT_LOCAL_TARBALLS_DIR}\"`"
130 # Some more sanity checks now that we have all paths set up
131 case "${CT_TARBALLS_DIR},${CT_SRC_DIR},${CT_BUILD_DIR},${CT_PREFIX_DIR},${CT_INSTALL_DIR}" in
132 *" "*) CT_Abort "Don't use spaces in paths, it breaks things.";;
135 # Check now if we can write to the destination directory:
136 if [ -d "${CT_INSTALL_DIR}" ]; then
137 CT_TestAndAbort "Destination directory \"${CT_INSTALL_DIR}\" is not removable" ! -w `dirname "${CT_INSTALL_DIR}"`
140 # Good, now grab a bit of informations on the system we're being run on,
141 # just in case something goes awok, and it's not our fault:
142 CT_SYS_USER="`id -un`"
143 CT_SYS_HOSTNAME=`hostname -f 2>/dev/null || true`
144 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
145 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-`uname -n`}"
146 CT_SYS_KERNEL=`uname -s`
147 CT_SYS_REVISION=`uname -r`
148 # MacOS X lacks '-o' :
149 CT_SYS_OS=`uname -o || echo "Unknown (maybe MacOS-X)"`
150 CT_SYS_MACHINE=`uname -m`
151 CT_SYS_PROCESSOR=`uname -p`
152 CT_SYS_GCC=`gcc -dumpversion`
153 CT_SYS_TARGET=`${CT_TOP_DIR}/tools/config.guess`
154 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
156 CT_DoLog EXTRA "Preparing working directories"
158 # Ah! The build directory shall be eradicated, even if we restart!
159 if [ -d "${CT_BUILD_DIR}" ]; then
160 mv "${CT_BUILD_DIR}" "${CT_BUILD_DIR}.$$"
161 chmod -R u+w "${CT_BUILD_DIR}.$$"
162 nohup rm -rf "${CT_BUILD_DIR}.$$" >/dev/null 2>&1 &
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 mv "${CT_TARBALLS_DIR}" "${CT_TARBALLS_DIR}.$$"
172 chmod -R u+w "${CT_TARBALLS_DIR}.$$"
173 nohup rm -rf "${CT_TARBALLS_DIR}.$$" >/dev/null 2>&1 &
175 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
176 mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
177 chmod -R u+w "${CT_SRC_DIR}.$$"
178 nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1 &
180 if [ -d "${CT_INSTALL_DIR}" ]; then
181 mv "${CT_INSTALL_DIR}" "${CT_INSTALL_DIR}.$$"
182 chmod -R u+w "${CT_INSTALL_DIR}.$$"
183 nohup rm -rf "${CT_INSTALL_DIR}.$$" >/dev/null 2>&1 &
185 if [ -d "${CT_DEBUG_INSTALL_DIR}" ]; then
186 mv "${CT_DEBUG_INSTALL_DIR}" "${CT_DEBUG_INSTALL_DIR}.$$"
187 chmod -R u+w "${CT_DEBUG_INSTALL_DIR}.$$"
188 nohup rm -rf "${CT_DEBUG_INSTALL_DIR}.$$" >/dev/null 2>&1 &
190 # In case we start anew, get rid of the previously saved state directory
191 if [ -d "${CT_STATE_DIR}" ]; then
192 mv "${CT_STATE_DIR}" "${CT_STATE_DIR}.$$"
193 chmod -R u+w "${CT_STATE_DIR}.$$"
194 nohup rm -rf "${CT_STATE_DIR}.$$" >/dev/null 2>&1 &
198 # Create the directories we'll use, even if restarting: it does no harm to
199 # create already existent directories, and CT_BUILD_DIR needs to be created
201 mkdir -p "${CT_TARBALLS_DIR}"
202 mkdir -p "${CT_SRC_DIR}"
203 mkdir -p "${CT_BUILD_DIR}"
204 mkdir -p "${CT_INSTALL_DIR}"
205 mkdir -p "${CT_PREFIX_DIR}"
206 mkdir -p "${CT_DEBUG_INSTALL_DIR}"
207 mkdir -p "${CT_CC_CORE_STATIC_PREFIX_DIR}"
208 mkdir -p "${CT_CC_CORE_SHARED_PREFIX_DIR}"
209 mkdir -p "${CT_STATE_DIR}"
211 # Kludge: CT_INSTALL_DIR and CT_PREFIX_DIR might have grown read-only if
212 # the previous build was successfull. To be able to move the logfile there,
213 # switch them back to read/write
214 chmod -R u+w "${CT_INSTALL_DIR}" "${CT_PREFIX_DIR}"
216 # Redirect log to the actual log file now we can
217 # It's quite understandable that the log file will be installed in the install
218 # directory, so we must first ensure it exists and is writeable (above) before
221 case "${CT_LOG_TO_FILE},${CT_LOG_FILE}" in
222 ,*) rm -f "${tmp_log_file}"
224 y,/*) mkdir -p "`dirname \"${CT_LOG_FILE}\"`"
225 cat "${tmp_log_file}" >>"${CT_LOG_FILE}"
226 rm -f "${tmp_log_file}"
227 exec >>"${CT_LOG_FILE}"
229 y,*) mkdir -p "`pwd`/`dirname \"${CT_LOG_FILE}\"`"
230 cat "${tmp_log_file}" >>"`pwd`/${CT_LOG_FILE}"
231 rm -f "${tmp_log_file}"
232 exec >>"${CT_LOG_FILE}"
236 # Setting up the rest of the environment only is not restarting
237 if [ -z "${CT_RESTART}" ]; then
238 # Determine build system if not set by the user
239 CT_Test "You did not specify the build system. That's OK, I can guess..." -z "${CT_BUILD}"
240 CT_BUILD="`${CT_TOP_DIR}/tools/config.sub \"${CT_BUILD:-\`${CT_TOP_DIR}/tools/config.guess\`}\"`"
242 # Arrange paths depending on wether we use sys-root or not.
243 if [ "${CT_USE_SYSROOT}" = "y" ]; then
244 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/sys-root"
245 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
246 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
247 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
248 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
250 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
251 # confused when $sysroot/usr/include is not present.
252 # Note: --prefix=/usr is magic!
253 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
255 # plain old way. All libraries in prefix/target/lib
256 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
257 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
258 # hack! Always use --with-sysroot for binutils.
259 # binutils 2.14 and later obey it, older binutils ignore it.
260 # Lets you build a working 32->64 bit cross gcc
261 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
262 # Use --with-headers, else final gcc will define disable_glibc while
263 # building libgcc, and you'll have no profiling
264 CC_CORE_SYSROOT_ARG="--without-headers"
265 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
266 LIBC_SYSROOT_ARG="prefix="
269 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
270 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail with
271 # "ld: cannot open crti.o: No such file or directory"
272 mkdir -p "${CT_SYSROOT_DIR}/lib"
273 mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
275 # Canadian-cross are really picky on the way they are built. Tweak the values.
276 CT_UNIQ_BUILD=`echo "${CT_BUILD}" |sed -r -e 's/-/-build_/'`
277 if [ "${CT_CANADIAN}" = "y" ]; then
278 # Arrange so that gcc never, ever think that build system == host system
279 CT_CANADIAN_OPT="--build=${CT_UNIQ_BUILD}"
280 # We shall have a compiler for this target!
283 CT_HOST="${CT_BUILD}"
284 CT_CANADIAN_OPT="--build=${CT_BUILD}"
285 # Add the target toolchain in the path so that we can build the C library
286 # Carefully add paths in the order we want them:
287 # - first try in ${CT_PREFIX_DIR}/bin
288 # - then try in ${CT_CC_CORE_SHARED_PREFIX_DIR}/bin
289 # - then try in ${CT_CC_CORE_STATIC_PREFIX_DIR}/bin
290 # - fall back to searching user's PATH
291 export PATH="${CT_PREFIX_DIR}/bin:${CT_CC_CORE_SHARED_PREFIX_DIR}/bin:${CT_CC_CORE_STATIC_PREFIX_DIR}/bin:${PATH}"
294 # Modify GCC_HOST to never be equal to $BUILD or $TARGET
295 # This strange operation causes gcc to always generate a cross-compiler
296 # even if the build machine is the same kind as the host.
297 # This is why CC has to be set when doing a canadian cross; you can't find a
298 # host compiler by appending -gcc to our whacky $GCC_HOST
299 # Kludge: it is reported that the above causes canadian crosses with cygwin
300 # hosts to fail, so avoid it just in that one case. It would be cleaner to
301 # just move this into the non-canadian case above, but I'm afraid that might
302 # cause some configure script somewhere to decide that since build==host, they
303 # could run host binaries.
304 # (Copied almost as-is from original crosstool):
305 case "${CT_KERNEL},${CT_CANADIAN}" in
307 *,y) CT_HOST="`echo \"${CT_HOST}\" |sed -r -e 's/-/-host_/;'`";;
310 # Ah! Recent versions of binutils need some of the build and/or host system
311 # (read CT_BUILD and CT_HOST) tools to be accessible (ar is but an example).
313 CT_DoLog EXTRA "Making build system tools available"
314 mkdir -p "${CT_PREFIX_DIR}/bin"
315 for tool in ar as dlltool gcc g++ gnatbind gnatmake ld nm ranlib strip windres objcopy objdump; do
316 if [ -n "`which ${tool}`" ]; then
317 ln -sfv "`which ${tool}`" "${CT_PREFIX_DIR}/bin/${CT_BUILD}-${tool}"
318 ln -sfv "`which ${tool}`" "${CT_PREFIX_DIR}/bin/${CT_UNIQ_BUILD}-${tool}"
319 ln -sfv "`which ${tool}`" "${CT_PREFIX_DIR}/bin/${CT_HOST}-${tool}"
323 # Ha. cygwin host have an .exe suffix (extension) for executables.
324 [ "${CT_KERNEL}" = "cygwin" ] && EXEEXT=".exe" || EXEEXT=""
326 # Transform the ARCH into a kernel-understandable ARCH
328 x86) CT_KERNEL_ARCH=i386;;
329 ppc) CT_KERNEL_ARCH=powerpc;;
330 *) CT_KERNEL_ARCH="${CT_ARCH}";;
333 # Build up the TARGET_CFLAGS from user-provided options
334 # Override with user-specified CFLAGS
335 [ -n "${CT_ARCH_CPU}" ] && CT_TARGET_CFLAGS="-mcpu=${CT_ARCH_CPU} ${CT_TARGET_CFLAGS}"
336 [ -n "${CT_ARCH_TUNE}" ] && CT_TARGET_CFLAGS="-mtune=${CT_ARCH_TUNE} ${CT_TARGET_CFLAGS}"
337 [ -n "${CT_ARCH_ARCH}" ] && CT_TARGET_CFLAGS="-march=${CT_ARCH_ARCH} ${CT_TARGET_CFLAGS}"
338 [ -n "${CT_ARCH_FPU}" ] && CT_TARGET_CFLAGS="-mfpu=${CT_ARCH_FPU} ${CT_TARGET_CFLAGS}"
342 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
344 # And help make go faster
346 [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
347 [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
349 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
350 CT_DoLog EXTRA "Building a toolchain for:"
351 CT_DoLog EXTRA " build = ${CT_BUILD}"
352 CT_DoLog EXTRA " host = ${CT_HOST}"
353 CT_DoLog EXTRA " target = ${CT_TARGET}"
354 set |egrep '^CT_.+=' |sort |CT_DoLog DEBUG
358 # Include sub-scripts instead of calling them: that way, we do not have to
359 # export any variable, nor re-parse the configuration and functions files.
360 . "${CT_TOP_DIR}/scripts/build/kernel_${CT_KERNEL}.sh"
361 . "${CT_TOP_DIR}/scripts/build/binutils.sh"
362 . "${CT_TOP_DIR}/scripts/build/libfloat.sh"
363 . "${CT_TOP_DIR}/scripts/build/libc_${CT_LIBC}.sh"
364 . "${CT_TOP_DIR}/scripts/build/cc_core_${CT_CC_CORE}.sh"
365 . "${CT_TOP_DIR}/scripts/build/cc_${CT_CC}.sh"
366 . "${CT_TOP_DIR}/scripts/build/debug.sh"
367 . "${CT_TOP_DIR}/scripts/build/tools.sh"
369 if [ -z "${CT_RESTART}" ]; then
370 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
381 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
382 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
383 mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
384 nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1
386 CT_DoStep INFO "Extracting and patching toolchain components"
399 # Now for the job by itself. Go have a coffee!
400 if [ "${CT_ONLY_DOWNLOAD}" != "y" -a "${CT_ONLY_EXTRACT}" != "y" ]; then
401 # Because of CT_RESTART, this becomes quite complex
404 [ -n "${CT_RESTART}" ] && do_it=0 || do_it=1
405 for step in libc_check_config \
406 kernel_check_config \
420 if [ ${do_it} -eq 0 ]; then
421 if [ "${CT_RESTART}" = "${step}" ]; then
422 CT_DoLoadState "${step}"
427 CT_DoSaveState ${step}
428 if [ ${do_stop} -eq 1 ]; then
429 CT_DoLog ERROR "Stopping just after step \"${prev_step}\", as requested."
433 if [ ${do_it} -eq 1 ]; then
435 if [ "${CT_STOP}" = "${step}" ]; then
438 if [ "${CTDEBUG_CT_PAUSE_STEPS}" = "y" ]; then
439 CT_DoPause "Step \"${step}\" finished"
445 # Create the aliases to the target tools
446 if [ -n "${CT_TARGET_ALIAS}" ]; then
447 CT_DoLog EXTRA "Creating symlinks from \"${CT_TARGET}-*\" to \"${CT_TARGET_ALIAS}-*\""
448 CT_Pushd "${CT_PREFIX_DIR}/bin"
449 for t in "${CT_TARGET}-"*; do
450 _t="`echo \"$t\" |sed -r -e 's/^'\"${CT_TARGET}\"'-/'\"${CT_TARGET_ALIAS}\"'-/;'`"
451 CT_DoLog DEBUG "Linking \"${_t}\" -> \"${t}\""
457 # Remove the generated documentation files
458 if [ "${CT_REMOVE_DOCS}" = "y" ]; then
459 CT_DoLog INFO "Removing installed documentation"
460 rm -rf "${CT_PREFIX_DIR}/"{,usr/}{man,info}
461 rm -rf "${CT_SYSROOT_DIR}/"{,usr/}{man,info}
462 rm -rf "${CT_DEBUG_INSTALL_DIR}/"{,usr/}{man,info}
465 CT_DoLog EXTRA "Removing access to the build system tools"
466 find "${CT_PREFIX_DIR}/bin" -name "${CT_BUILD}-"'*' -exec rm -fv {} \+ |CT_DoLog DEBUG
467 find "${CT_PREFIX_DIR}/bin" -name "${CT_UNIQ_BUILD}-"'*' -exec rm -fv {} \+ |CT_DoLog DEBUG
468 find "${CT_PREFIX_DIR}/bin" -name "${CT_HOST}-"'*' -exec rm -fv {} \+ |CT_DoLog DEBUG
471 # OK, now we're done, set the toolchain read-only
472 # Don't log, the log file may become read-only any moment...
473 chmod -R a-w "${CT_INSTALL_DIR}"
475 # We still have some small bits to log
476 chmod u+w "${CT_LOG_FILE}"
480 # All files should now be read-only, log file included
481 chmod a-w "${CT_LOG_FILE}"