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>

 # Compute AVR32-specific values

 CT_DoArchTupleValues() {

     # The architecture part of the tuple:

     CT_TARGET_ARCH="${CT_ARCH}"

     # gcc ./configure flags

     CT_ARCH_WITH_ARCH=

     CT_ARCH_WITH_ABI=

     CT_ARCH_WITH_CPU=

     CT_ARCH_WITH_TUNE=

     CT_ARCH_WITH_FPU=

     CT_ARCH_WITH_FLOAT=

     CT_TARGET_SYS=none

 }