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 checks for needed tools. It eventually calls the main build script.
15 # User must set CT_TOP_DIR in is environment!
16 # Once we can build out-of-tree, then this will have to go.
17 if [ -z "${CT_TOP_DIR}" -o ! -d "${CT_TOP_DIR}" ]; then
18 # We don't have the functions right now, because we don't have CT_TOP_DIR.
19 # Do the print stuff by hand:
20 echo "CT_TOP_DIR not set. You must set CT_TOP_DIR to the top directory where crosstool is installed."
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`
30 # Log to a temporary file until we have built our environment
31 CT_ACTUAL_LOG_FILE="${CT_TOP_DIR}/$$.log"
33 # CT_TOP_DIR should be an absolute path.
34 CT_TOP_DIR="`CT_MakeAbsolutePath \"${CT_TOP_DIR}\"`"
36 # Parse the configuration file
37 CT_TestOrAbort "Configuration file not found. Please create one." -f "${CT_TOP_DIR}/.config"
38 . "${CT_TOP_DIR}/.config"
40 # Override the color scheme if needed
41 if [ "${CT_LOG_USE_COLORS}" = "y" ]; then
42 CT_ERROR_COLOR="${_A_NOR}${_A_BRI}${_F_RED}"
43 CT_WARN_COLOR="${_A_NOR}${_A_BRI}${_F_YEL}"
44 CT_INFO_COLOR="${_A_NOR}${_A_BRI}${_F_GRN}"
45 CT_EXTRA_COLOR="${_A_NOR}${_A_DIM}${_F_GRN}"
46 CT_DEBUG_COLOR="${_A_NOR}${_A_BRI}${_F_BLU}"
47 CT_ALL_COLOR="${_A_NOR}${_A_DIM}${_F_WHI}"
48 CT_NORMAL_COLOR="${_A_NOR}"
59 # Yes! We can do full logging from now on!
60 CT_DoLog INFO "Build started ${CT_STAR_DATE_HUMAN}"
63 renice ${CT_NICE} $$ |CT_DoLog DEBUG
65 # Some sanity checks in the environment and needed tools
66 CT_DoLog INFO "Checking environment sanity"
68 # Enable known ordering of files in directory listings:
69 CT_Test "Crosstool-NG might not work as expected with LANG=\"${LANG}\"" -n "${LANG}"
70 case "${LC_COLLATE},${LC_ALL}" in
71 # These four combinations are known to sort files in the correct order:
76 # Anything else is destined to be borked if not gracefuly handled:
77 *) CT_DoLog WARN "Either LC_COLLATE=\"${LC_COLLATE}\" or LC_ALL=\"${LC_ALL}\" is not supported."
78 export LC_ALL=`locale -a |egrep "^(fr_FR|en_US)" |head -n 1`
79 CT_TestOrAbort "Neither en_US* nor fr_FR* locales found on your system." -n "${LC_ALL}"
80 CT_DoLog WARN "Forcing to known working LC_ALL=\"${LC_ALL}\"."
84 # Other environment sanity checks
85 CT_TestAndAbort "Don't set LD_LIBRARY_PATH. It screws up the build." -n "${LD_LIBRARY_PATH}"
86 CT_TestAndAbort "Don't set CFLAGS. It screws up the build." -n "${CFLAGS}"
87 CT_TestAndAbort "Don't set CXXFLAGS. It screws up the build." -n "${CXXFLAGS}"
88 CT_Test "GREP_OPTIONS screws up the build. Resetting." -n "${GREP_OPTIONS}"
95 CT_DoStep DEBUG "Dumping crosstool-NG configuration"
96 cat ${CT_TOP_DIR}/.config |egrep '^(# |)CT_' |CT_DoLog DEBUG
99 CT_DoLog INFO "Building environment variables"
101 # Target triplet: CT_TARGET needs a little love:
102 CT_DoBuildTargetTriplet
104 # Now, build up the variables from the user-configured options.
105 CT_KERNEL_FILE="${CT_KERNEL}-${CT_KERNEL_VERSION}"
106 CT_BINUTILS_FILE="binutils-${CT_BINUTILS_VERSION}"
107 if [ "${CT_CC_USE_CORE}" != "y" ]; then
108 CT_CC_CORE="${CT_CC}"
109 CT_CC_CORE_VERSION="${CT_CC_VERSION}"
110 CT_CC_CORE_EXTRA_CONFIG="${CT_CC_EXTRA_CONFIG}"
112 CT_CC_CORE_FILE="${CT_CC_CORE}-${CT_CC_CORE_VERSION}"
113 CT_CC_FILE="${CT_CC}-${CT_CC_VERSION}"
114 CT_LIBC_FILE="${CT_LIBC}-${CT_LIBC_VERSION}"
115 [ "${CT_ARCH_FLOAT_SW_LIBFLOAT}" = "y" ] && CT_LIBFLOAT_FILE="libfloat-990616"
117 # Kludge: If any of the configured options needs CT_TARGET or CT_TOP_DIR,
118 # then rescan the options file now:
119 . "${CT_TOP_DIR}/.config"
121 # Where will we work?
122 CT_TARBALLS_DIR="${CT_TOP_DIR}/targets/tarballs"
123 CT_SRC_DIR="${CT_TOP_DIR}/targets/${CT_TARGET}/src"
124 CT_BUILD_DIR="${CT_TOP_DIR}/targets/${CT_TARGET}/build"
126 # Make all path absolute, it so much easier!
127 CT_LOCAL_TARBALLS_DIR="`CT_MakeAbsolutePath \"${CT_LOCAL_TARBALLS_DIR}\"`"
129 # Some more sanity checks now that we have all paths set up
130 case "${CT_TARBALLS_DIR},${CT_SRC_DIR},${CT_BUILD_DIR},${CT_PREFIX_DIR},${CT_INSTALL_DIR}" in
131 *" "*) CT_Abort "Don't use spaces in paths, it breaks things.";;
134 # Check now if we can write to the destination directory:
135 if [ -d "${CT_INSTALL_DIR}" ]; then
136 CT_TestAndAbort "Destination directory \"${CT_INSTALL_DIR}\" is not removable" ! -w `dirname "${CT_INSTALL_DIR}"`
139 # Get rid of pre-existing installed toolchain and previous build directories.
140 # We need to do that _before_ we can safely log, because the log file will
141 # most probably be in the toolchain directory.
142 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
143 mv "${CT_TARBALLS_DIR}" "${CT_TARBALLS_DIR}.$$"
144 nohup rm -rf "${CT_TARBALLS_DIR}.$$" >/dev/null 2>&1 &
146 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
147 mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
148 nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1 &
150 if [ -d "${CT_BUILD_DIR}" ]; then
151 mv "${CT_BUILD_DIR}" "${CT_BUILD_DIR}.$$"
152 nohup rm -rf "${CT_BUILD_DIR}.$$" >/dev/null 2>&1 &
154 if [ -d "${CT_INSTALL_DIR}" ]; then
155 mv "${CT_INSTALL_DIR}" "${CT_INSTALL_DIR}.$$"
156 nohup rm -rf "${CT_INSTALL_DIR}.$$" >/dev/null 2>&1 &
159 # Note: we'll always install the core compiler in its own directory, so as to
160 # not mix the two builds: core and final. Anyway, its generic, wether we use
161 # a different compiler as core, or not.
162 CT_CC_CORE_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core"
164 # Create the directories we'll use
165 mkdir -p "${CT_TARBALLS_DIR}"
166 mkdir -p "${CT_SRC_DIR}"
167 mkdir -p "${CT_BUILD_DIR}"
168 mkdir -p "${CT_INSTALL_DIR}"
169 mkdir -p "${CT_CC_CORE_PREFIX_DIR}"
171 # Good, now grab a bit of informations on the system we're being run,
172 # just in case something goes awok, and it's not our fault:
173 CT_SYS_HOSTNAME=`hostname -f 2>/dev/null || true`
174 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
175 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-`uname -n`}"
176 CT_SYS_KERNEL=`uname -s`
177 CT_SYS_REVISION=`uname -r`
178 # MacOS X lacks '-o' :
179 CT_SYS_OS=`uname -o || echo "Unknown (maybe MacOS-X)"`
180 CT_SYS_MACHINE=`uname -m`
181 CT_SYS_PROCESSOR=`uname -p`
182 CT_SYS_USER="`id -un`"
183 CT_SYS_DATE=`CT_DoDate +%Y%m%d.%H%M%S`
184 CT_SYS_GCC=`gcc -dumpversion`
185 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_SYS_DATE} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME} for ${CT_TARGET}"
187 # Redirect log to the actual log file now we can
188 # It's quite understandable that the log file will be installed in the install
189 # directory, so we must first ensure it exists and is writeable (above) before
191 case "${CT_LOG_TO_FILE},${CT_LOG_FILE}" in
192 ,*) rm -f "${CT_ACTUAL_LOG_FILE}"
193 CT_ACTUAL_LOG_FILE=/dev/null
195 y,/*) mkdir -p "`dirname \"${CT_LOG_FILE}\"`"
196 mv "${CT_ACTUAL_LOG_FILE}" "${CT_LOG_FILE}"
197 CT_ACTUAL_LOG_FILE="${CT_LOG_FILE}"
199 y,*) mkdir -p "`pwd`/`dirname \"${CT_LOG_FILE}\"`"
200 mv "${CT_ACTUAL_LOG_FILE}" "`pwd`/${CT_LOG_FILE}"
201 CT_ACTUAL_LOG_FILE="`pwd`/${CT_LOG_FILE}"
205 # Determine build system if not set by the user
206 CT_Test "You did not specify the build system. Guessing." -z "${CT_BUILD}"
207 CT_BUILD="`${CT_TOP_DIR}/tools/config.sub \"${CT_BUILD:-\`${CT_TOP_DIR}/tools/config.guess\`}\"`"
209 # Arrange paths depending on wether we use sys-root or not.
210 if [ "${CT_USE_SYSROOT}" = "y" ]; then
211 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/sys-root"
212 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
213 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
214 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
215 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
217 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
218 # confused when $sysroot/usr/include is not present.
219 # Note: --prefix=/usr is magic!
220 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
222 # plain old way. All libraries in prefix/target/lib
223 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
224 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
225 # hack! Always use --with-sysroot for binutils.
226 # binutils 2.14 and later obey it, older binutils ignore it.
227 # Lets you build a working 32->64 bit cross gcc
228 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
229 # Use --with-headers, else final gcc will define disable_glibc while
230 # building libgcc, and you'll have no profiling
231 CC_CORE_SYSROOT_ARG="--without-headers"
232 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
233 LIBC_SYSROOT_ARG="prefix="
236 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
237 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail with
238 # "ld: cannot open crti.o: No such file or directory"
239 mkdir -p "${CT_SYSROOT_DIR}/lib"
240 mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
242 # Canadian-cross are really picky on the way they are built. Tweak the values.
243 if [ "${CT_CANADIAN}" = "y" ]; then
244 # Arrange so that gcc never, ever think that build system == host system
245 CT_CANADIAN_OPT="--build=`echo \"${CT_BUILD}\" |sed -r -e 's/-/-build_/'`"
246 # We shall have a compiler for this target!
249 CT_HOST="${CT_BUILD}"
251 # Add the target toolchain in the path so that we can build the C library
252 export PATH="${CT_PREFIX_DIR}/bin:${CT_CC_CORE_PREFIX_DIR}/bin:${PATH}"
255 # Modify GCC_HOST to never be equal to $BUILD or $TARGET
256 # This strange operation causes gcc to always generate a cross-compiler
257 # even if the build machine is the same kind as the host.
258 # This is why CC has to be set when doing a canadian cross; you can't find a
259 # host compiler by appending -gcc to our whacky $GCC_HOST
260 # Kludge: it is reported that the above causes canadian crosses with cygwin
261 # hosts to fail, so avoid it just in that one case. It would be cleaner to
262 # just move this into the non-canadian case above, but I'm afraid that might
263 # cause some configure script somewhere to decide that since build==host, they
264 # could run host binaries.
265 # (Copied almost as-is from original crosstool):
266 case "${CT_KERNEL},${CT_CANADIAN}" in
268 *) CT_HOST="`echo \"${CT_HOST}\" |sed -r -e 's/-/-host_/;'`";;
271 # Ah! Recent versions of binutils need some of the build and/or host system
272 # (read CT_BUILD and CT_HOST) tools to be accessible (ar is but an example).
274 CT_DoLog EXTRA "Making build system tools available"
275 mkdir -p "${CT_PREFIX_DIR}/bin"
277 ln -s "`which ${tool}`" "${CT_PREFIX_DIR}/bin/${CT_BUILD}-${tool}"
278 ln -s "`which ${tool}`" "${CT_PREFIX_DIR}/bin/${CT_HOST}-${tool}"
281 # Ha. cygwin host have an .exe suffix (extension) for executables.
282 [ "${CT_KERNEL}" = "cygwin" ] && EXEEXT=".exe" || EXEEXT=""
284 # Transform the ARCH into a kernel-understandable ARCH
286 x86) CT_KERNEL_ARCH=i386;;
287 ppc) CT_KERNEL_ARCH=powerpc;;
288 *) CT_KERNEL_ARCH="${CT_ARCH}";;
291 # Build up the TARGET_CFLAGS from user-provided options
292 # Override with user-specified CFLAGS
293 [ -n "${CT_ARCH_CPU}" ] && CT_TARGET_CFLAGS="-mcpu=${CT_ARCH_CPU} ${CT_TARGET_CFLAGS}"
294 [ -n "${CT_ARCH_TUNE}" ] && CT_TARGET_CFLAGS="-mtune=${CT_ARCH_TUNE} ${CT_TARGET_CFLAGS}"
295 [ -n "${CT_ARCH_ARCH}" ] && CT_TARGET_CFLAGS="-march=${CT_ARCH_ARCH} ${CT_TARGET_CFLAGS}"
296 [ -n "${CT_ARCH_FPU}" ] && CT_TARGET_CFLAGS="-mfpu=${CT_ARCH_FPU} ${CT_TARGET_CFLAGS}"
300 [ "${CT_USE_PIPES}" = "y" ] && CT_CFLAGS_FOR_HOST="${CT_CFLAGS_FOR_HOST} -pipe"
302 # And help make go faster
304 [ ${CT_PARALLEL_JOBS} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -j${CT_PARALLEL_JOBS}"
305 [ ${CT_LOAD} -ne 0 ] && PARALLELMFLAGS="${PARALLELMFLAGS} -l${CT_LOAD}"
307 CT_DoStep EXTRA "Dumping internal crosstool-NG configuration"
308 CT_DoLog EXTRA "Building a toolchain for:"
309 CT_DoLog EXTRA " build = ${CT_BUILD}"
310 CT_DoLog EXTRA " host = ${CT_HOST}"
311 CT_DoLog EXTRA " target = ${CT_TARGET}"
312 set |egrep '^CT_.+=' |sort |CT_DoLog DEBUG
315 # Include sub-scripts instead of calling them: that way, we do not have to
316 # export any variable, nor re-parse the configuration and functions files.
317 . "${CT_TOP_DIR}/scripts/build/kernel_${CT_KERNEL}.sh"
318 . "${CT_TOP_DIR}/scripts/build/binutils.sh"
319 . "${CT_TOP_DIR}/scripts/build/libfloat.sh"
320 . "${CT_TOP_DIR}/scripts/build/libc_${CT_LIBC}.sh"
321 . "${CT_TOP_DIR}/scripts/build/cc_core_${CT_CC_CORE}.sh"
322 . "${CT_TOP_DIR}/scripts/build/cc_${CT_CC}.sh"
324 # Now for the job by itself. Go have a coffee!
325 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
334 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
335 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
336 mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
337 nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1
339 CT_DoStep INFO "Extracting and patching toolchain components"
348 if [ "${CT_ONLY_EXTRACT}" != "y" ]; then
350 do_kernel_check_config
360 # Create the aliases to the target tools
361 if [ -n "${CT_TARGET_ALIAS}" ]; then
362 CT_DoLog EXTRA "Creating symlinks from \"${CT_TARGET}-*\" to \"${CT_TARGET_ALIAS}-*\""
363 CT_Pushd "${CT_PREFIX_DIR}/bin"
364 for t in "${CT_TARGET}-"*; do
365 _t="`echo \"$t\" |sed -r -e 's/^'\"${CT_TARGET}\"'-/'\"${CT_TARGET_ALIAS}\"'-/;'`"
366 CT_DoLog DEBUG "Linking \"${_t}\" -> \"${t}\""
372 # Remove the generated documentation files
373 if [ "${CT_REMOVE_DOCS}" = "y" ]; then
374 CT_DoLog INFO "Removing installed documentation"
375 rm -rf "${CT_PREFIX_DIR}/"{man,info}
380 CT_STOP_DATE=`CT_DoDate +%s%N`
381 CT_STOP_DATE_HUMAN=`CT_DoDate +%Y%m%d.%H%M%S`
382 CT_DoLog INFO "Build completed at ${CT_STOP_DATE_HUMAN}"
383 elapsed=$((CT_STOP_DATE-CT_STAR_DATE))
384 elapsed_min=$((elapsed/(60*1000*1000*1000)))
385 elapsed_sec=`printf "%02d" $(((elapsed%(60*1000*1000*1000))/(1000*1000*1000)))`
386 elapsed_csec=`printf "%02d" $(((elapsed%(1000*1000*1000))/(10*1000*1000)))`
387 CT_DoLog INFO "(elapsed: ${elapsed_min}:${elapsed_sec}.${elapsed_csec})"
389 # Restore a 'normal' color setting
390 echo -en "${CT_NORMAL_COLOR}"