scripts, cc/gcc: do not fail on existing symlinks or build.log
If the user builds a toolchain over an existing one, so, without removing
CT_PREFIX_DIR, the build fails as the symlinks already exist, as does the
build.log.
This can also happen (for build.log) if the user first ran in download-
or extract-only.
Patch (with no SoB) originally from:
Phil Wilshire <phil.wilshire@overturenetworks.com>
Modified by me as it did not apply cleanly.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
1 # Build script for automake
3 CT_AUTOMAKE_VERSION=1.11.1
5 do_companion_tools_automake_get() {
6 CT_GetFile "automake-${CT_AUTOMAKE_VERSION}" \
7 {ftp,http}://ftp.gnu.org/gnu/automake
10 do_companion_tools_automake_extract() {
11 CT_Extract "automake-${CT_AUTOMAKE_VERSION}"
12 CT_DoExecLog ALL chmod -R u+w "${CT_SRC_DIR}/automake-${CT_AUTOMAKE_VERSION}"
13 CT_Patch "automake" "${CT_AUTOMAKE_VERSION}"
16 do_companion_tools_automake_build() {
17 CT_DoStep EXTRA "Installing automake"
18 mkdir -p "${CT_BUILD_DIR}/build-automake"
19 CT_Pushd "${CT_BUILD_DIR}/build-automake"
22 "${CT_SRC_DIR}/automake-${CT_AUTOMAKE_VERSION}/configure" \
23 --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"
25 CT_DoExecLog ALL make install