scripts: leave changelog in build dir, copy to install dir

Users tend to look for the build log in the current working directory,
rather than in the toolchain's installation dir. While bundling the build
log in the toolchain installation dir is nice for distribution and review,
it can be easier to have the build log readily available in the working
directory, as it is quicker to get to it.

So, the build log stays in the working directory until the toolchain is
completely and successfully built, and then a (compressed) copy is made.

Reported-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

# Build script for m4

CT_M4_VERSION=1.4.13

do_companion_tools_m4_get() {

    CT_GetFile "m4-${CT_M4_VERSION}" \

               {ftp,http}://ftp.gnu.org/gnu/m4

}

do_companion_tools_m4_extract() {

    CT_Extract "m4-${CT_M4_VERSION}"

    CT_Patch "m4" "${CT_M4_VERSION}"

}

do_companion_tools_m4_build() {

    CT_DoStep EXTRA "Installing m4"

    mkdir -p "${CT_BUILD_DIR}/build-m4"

    CT_Pushd "${CT_BUILD_DIR}/build-m4"

    CT_DoExecLog CFG \

    "${CT_SRC_DIR}/m4-${CT_M4_VERSION}/configure" \

        --prefix="${CT_BUILDTOOLS_PREFIX_DIR}"

    CT_DoExecLog ALL make

    CT_DoExecLog ALL make install

    CT_Popd

    CT_EndStep

}