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>

 diff -dur strace-4.5.16.orig/syscall.c strace-4.5.16/syscall.c

 --- strace-4.5.16.orig/syscall.c	2007-07-14 19:21:44.000000000 +0200

 +++ strace-4.5.16/syscall.c	2007-07-14 19:22:49.000000000 +0200

 @@ -125,6 +125,18 @@

  #define TP TRACE_PROCESS

  #define TS TRACE_SIGNAL

 +#ifndef HAVE_STATFS64

 +/*

 + * Ugly hacks for systems that do not have LFS

 + */

 +

 +#define sys_truncate64  sys_truncate

 +#define sys_ftruncate64 sys_ftruncate

 +#define sys_getdents64  sys_getdents

 +#define sys_statfs64    sys_statfs

 +#define sys_fstatfs64   sys_fstatfs

 +#endif

 +

  static const struct sysent sysent0[] = {

  #include "syscallent.h"

  };