Move the config script for the build dir to the source dir.
That will be useful when we have the restart functionality.
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 # - what goes to the log file goes to fd #1 (stdout)
32 # - what goes to the screen goes to fd #6
33 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/${CT_TARGET}/src"
109 CT_BUILD_DIR="${CT_TOP_DIR}/targets/${CT_TARGET}/build"
110 CT_DEBUG_INSTALL_DIR="${CT_INSTALL_DIR}/${CT_TARGET}/debug-root"
112 # Make all path absolute, it so much easier!
113 CT_LOCAL_TARBALLS_DIR="`CT_MakeAbsolutePath \"${CT_LOCAL_TARBALLS_DIR}\"`"
115 # Some more sanity checks now that we have all paths set up
116 case "${CT_TARBALLS_DIR},${CT_SRC_DIR},${CT_BUILD_DIR},${CT_PREFIX_DIR},${CT_INSTALL_DIR}" in
117 *" "*) CT_Abort "Don't use spaces in paths, it breaks things.";;
120 # Check now if we can write to the destination directory:
121 if [ -d "${CT_INSTALL_DIR}" ]; then
122 CT_TestAndAbort "Destination directory \"${CT_INSTALL_DIR}\" is not removable" ! -w `dirname "${CT_INSTALL_DIR}"`
125 # Good, now grab a bit of informations on the system we're being run on,
126 # just in case something goes awok, and it's not our fault:
127 CT_SYS_USER="`id -un`"
128 CT_SYS_HOSTNAME=`hostname -f 2>/dev/null || true`
129 # Hmmm. Some non-DHCP-enabled machines do not have an FQDN... Fall back to node name.
130 CT_SYS_HOSTNAME="${CT_SYS_HOSTNAME:-`uname -n`}"
131 CT_SYS_KERNEL=`uname -s`
132 CT_SYS_REVISION=`uname -r`
133 # MacOS X lacks '-o' :
134 CT_SYS_OS=`uname -o || echo "Unknown (maybe MacOS-X)"`
135 CT_SYS_MACHINE=`uname -m`
136 CT_SYS_PROCESSOR=`uname -p`
137 CT_SYS_GCC=`gcc -dumpversion`
138 CT_SYS_TARGET=`${CT_TOP_DIR}/tools/config.guess`
139 CT_TOOLCHAIN_ID="crosstool-${CT_VERSION} build ${CT_STAR_DATE_HUMAN} by ${CT_SYS_USER}@${CT_SYS_HOSTNAME}"
141 CT_DoLog EXTRA "Preparing working directories"
143 # Get rid of pre-existing installed toolchain and previous build directories.
144 # We need to do that _before_ we can safely log, because the log file will
145 # most probably be in the toolchain directory.
146 if [ "${CT_FORCE_DOWNLOAD}" = "y" -a -d "${CT_TARBALLS_DIR}" ]; then
147 mv "${CT_TARBALLS_DIR}" "${CT_TARBALLS_DIR}.$$"
148 chmod -R u+w "${CT_TARBALLS_DIR}.$$"
149 nohup rm -rf "${CT_TARBALLS_DIR}.$$" >/dev/null 2>&1 &
151 if [ "${CT_FORCE_EXTRACT}" = "y" -a -d "${CT_SRC_DIR}" ]; then
152 mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
153 chmod -R u+w "${CT_SRC_DIR}.$$"
154 nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1 &
156 if [ -d "${CT_BUILD_DIR}" ]; then
157 mv "${CT_BUILD_DIR}" "${CT_BUILD_DIR}.$$"
158 chmod -R u+w "${CT_BUILD_DIR}.$$"
159 nohup rm -rf "${CT_BUILD_DIR}.$$" >/dev/null 2>&1 &
161 if [ -d "${CT_INSTALL_DIR}" ]; then
162 mv "${CT_INSTALL_DIR}" "${CT_INSTALL_DIR}.$$"
163 chmod -R u+w "${CT_INSTALL_DIR}.$$"
164 nohup rm -rf "${CT_INSTALL_DIR}.$$" >/dev/null 2>&1 &
166 if [ -d "${CT_DEBUG_INSTALL_DIR}" ]; then
167 mv "${CT_DEBUG_INSTALL_DIR}" "${CT_DEBUG_INSTALL_DIR}.$$"
168 chmod -R u+w "${CT_DEBUG_INSTALL_DIR}.$$"
169 nohup rm -rf "${CT_DEBUG_INSTALL_DIR}.$$" >/dev/null 2>&1 &
172 # Note: we'll always install the core compiler in its own directory, so as to
173 # not mix the two builds: core and final. Anyway, its generic, wether we use
174 # a different compiler as core, or not.
175 CT_CC_CORE_PREFIX_DIR="${CT_BUILD_DIR}/${CT_CC}-core"
177 # Create the directories we'll use
178 mkdir -p "${CT_TARBALLS_DIR}"
179 mkdir -p "${CT_SRC_DIR}"
180 mkdir -p "${CT_BUILD_DIR}"
181 mkdir -p "${CT_INSTALL_DIR}"
182 mkdir -p "${CT_DEBUG_INSTALL_DIR}"
183 mkdir -p "${CT_CC_CORE_PREFIX_DIR}"
185 # Redirect log to the actual log file now we can
186 # It's quite understandable that the log file will be installed in the install
187 # directory, so we must first ensure it exists and is writeable (above) before
190 case "${CT_LOG_TO_FILE},${CT_LOG_FILE}" in
191 ,*) rm -f "${tmp_log_file}"
193 y,/*) mkdir -p "`dirname \"${CT_LOG_FILE}\"`"
194 mv "${tmp_log_file}" "${CT_LOG_FILE}"
195 exec >>"${CT_LOG_FILE}"
197 y,*) mkdir -p "`pwd`/`dirname \"${CT_LOG_FILE}\"`"
198 mv "${tmp_log_file}" "`pwd`/${CT_LOG_FILE}"
199 exec >>"${CT_LOG_FILE}"
203 # Determine build system if not set by the user
204 CT_Test "You did not specify the build system. That's OK, I can guess..." -z "${CT_BUILD}"
205 CT_BUILD="`${CT_TOP_DIR}/tools/config.sub \"${CT_BUILD:-\`${CT_TOP_DIR}/tools/config.guess\`}\"`"
207 # Arrange paths depending on wether we use sys-root or not.
208 if [ "${CT_USE_SYSROOT}" = "y" ]; then
209 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}/sys-root"
210 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/usr/include"
211 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
212 CC_CORE_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
213 CC_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
215 # glibc's prefix must be exactly /usr, else --with-sysroot'd gcc will get
216 # confused when $sysroot/usr/include is not present.
217 # Note: --prefix=/usr is magic!
218 # See http://www.gnu.org/software/libc/FAQ.html#s-2.2
220 # plain old way. All libraries in prefix/target/lib
221 CT_SYSROOT_DIR="${CT_PREFIX_DIR}/${CT_TARGET}"
222 CT_HEADERS_DIR="${CT_SYSROOT_DIR}/include"
223 # hack! Always use --with-sysroot for binutils.
224 # binutils 2.14 and later obey it, older binutils ignore it.
225 # Lets you build a working 32->64 bit cross gcc
226 BINUTILS_SYSROOT_ARG="--with-sysroot=${CT_SYSROOT_DIR}"
227 # Use --with-headers, else final gcc will define disable_glibc while
228 # building libgcc, and you'll have no profiling
229 CC_CORE_SYSROOT_ARG="--without-headers"
230 CC_SYSROOT_ARG="--with-headers=${CT_HEADERS_DIR}"
231 LIBC_SYSROOT_ARG="prefix="
234 # Prepare the 'lib' directories in sysroot, else the ../lib64 hack used by
235 # 32 -> 64 bit crosscompilers won't work, and build of final gcc will fail with
236 # "ld: cannot open crti.o: No such file or directory"
237 mkdir -p "${CT_SYSROOT_DIR}/lib"
238 mkdir -p "${CT_SYSROOT_DIR}/usr/lib"
240 # Canadian-cross are really picky on the way they are built. Tweak the values.
241 if [ "${CT_CANADIAN}" = "y" ]; then
242 # Arrange so that gcc never, ever think that build system == host system
243 CT_CANADIAN_OPT="--build=`echo \"${CT_BUILD}\" |sed -r -e 's/-/-build_/'`"
244 # We shall have a compiler for this target!
247 CT_HOST="${CT_BUILD}"
249 # Add the target toolchain in the path so that we can build the C library
250 export PATH="${CT_PREFIX_DIR}/bin:${CT_CC_CORE_PREFIX_DIR}/bin:${PATH}"
253 # Modify GCC_HOST to never be equal to $BUILD or $TARGET
254 # This strange operation causes gcc to always generate a cross-compiler
255 # even if the build machine is the same kind as the host.
256 # This is why CC has to be set when doing a canadian cross; you can't find a
257 # host compiler by appending -gcc to our whacky $GCC_HOST
258 # Kludge: it is reported that the above causes canadian crosses with cygwin
259 # hosts to fail, so avoid it just in that one case. It would be cleaner to
260 # just move this into the non-canadian case above, but I'm afraid that might
261 # cause some configure script somewhere to decide that since build==host, they
262 # could run host binaries.
263 # (Copied almost as-is from original crosstool):
264 case "${CT_KERNEL},${CT_CANADIAN}" in
266 *) CT_HOST="`echo \"${CT_HOST}\" |sed -r -e 's/-/-host_/;'`";;
269 # Ah! Recent versions of binutils need some of the build and/or host system
270 # (read CT_BUILD and CT_HOST) tools to be accessible (ar is but an example).
272 CT_DoLog EXTRA "Making build system tools available"
273 mkdir -p "${CT_PREFIX_DIR}/bin"
274 for tool in ar gcc; do
275 ln -s "`which ${tool}`" "${CT_PREFIX_DIR}/bin/${CT_BUILD}-${tool}"
276 case "${CT_TOOLCHAIN_TYPE}" in
277 cross|native) 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"
323 . "${CT_TOP_DIR}/scripts/build/debug.sh"
325 # Now for the job by itself. Go have a coffee!
326 CT_DoStep INFO "Retrieving needed toolchain components' tarballs"
336 if [ "${CT_ONLY_DOWNLOAD}" != "y" ]; then
337 if [ "${CT_FORCE_EXTRACT}" = "y" ]; then
338 mv "${CT_SRC_DIR}" "${CT_SRC_DIR}.$$"
339 nohup rm -rf "${CT_SRC_DIR}.$$" >/dev/null 2>&1
341 CT_DoStep INFO "Extracting and patching toolchain components"
351 if [ "${CT_ONLY_EXTRACT}" != "y" ]; then
353 do_kernel_check_config
364 # Create the aliases to the target tools
365 if [ -n "${CT_TARGET_ALIAS}" ]; then
366 CT_DoLog EXTRA "Creating symlinks from \"${CT_TARGET}-*\" to \"${CT_TARGET_ALIAS}-*\""
367 CT_Pushd "${CT_PREFIX_DIR}/bin"
368 for t in "${CT_TARGET}-"*; do
369 _t="`echo \"$t\" |sed -r -e 's/^'\"${CT_TARGET}\"'-/'\"${CT_TARGET_ALIAS}\"'-/;'`"
370 CT_DoLog DEBUG "Linking \"${_t}\" -> \"${t}\""
376 # Remove the generated documentation files
377 if [ "${CT_REMOVE_DOCS}" = "y" ]; then
378 CT_DoLog INFO "Removing installed documentation"
379 rm -rf "${CT_PREFIX_DIR}/"{,usr/}{man,info}
380 rm -rf "${CT_SYSROOT_DIR}/"{,usr/}{man,info}
381 rm -rf "${CT_DEBUG_INSTALL_DIR}/"{,usr/}{man,info}
386 # OK, now we're done, set the toolchain read-only
387 # Don't log, the log file may become read-only any moment...
388 chmod -R a-w "${CT_INSTALL_DIR}"
390 # We stil have some small bits to log
391 chmod u+w "${CT_LOG_FILE}"
395 # All files should now be read-only, log-file included
396 chmod a-w "${CT_LOG_FILE}"
398 # Restore a 'normal' color setting
399 echo -en "${CT_NORMAL_COLOR}"