scripts/patch-renumber.sh
author Daniel Price <daniel.price@gmail.com>
Tue Nov 20 16:59:17 2012 -0800 (2012-11-20)
changeset 3126 333d3e40cbd1
parent 1623 f935634ef900
permissions -rwxr-xr-x
scripts: refine static linking check to better guide the user

The current mechanism to check if static linking is possible, and the mesage
displayed on failure, can be puzzling to the unsuspecting user.

Also, the current implementation is not using the existing infrastructure,
and is thus difficult to enhance with new tests.

So, switch to using the standard CT_DoExecLog infra, and use four tests to
check for the host compiler:
- check we can run it
- check it can build a trivial program
- check it can statically link that program
- check if it statically link with libstdc++

That should cover most of the problems. Hopefully.

(At the same time, fix a typo in a comment)

Signed-off-by: Daniel Price <daniel.price@gmail.com>
[yann.morin.1998@free.fr: split original patch for self-contained changes]
[yann.morin.1998@free.fr: use steps to better see gcc's output]
[yann.morin.1998@free.fr: commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Message-Id: <163f86b5216fc08c672a.1353459722@nipigon.dssd.com>
Patchwork-Id: 200536
     1 #!/bin/sh
     2 # Yes, this intends to be a true POSIX script file.
     3 set -e
     4 
     5 myname="$0"
     6 
     7 # Parse the tools' paths configuration
     8 # It is expected that this script is only to be run from the
     9 # source directory of crosstool-NG, so it is trivial to find
    10 # paths.sh (we can't use  ". paths.sh", as POSIX states that
    11 # $PATH should be searched for, and $PATH most probably doe
    12 # not include "."), hence the "./".
    13 . "./paths.sh"
    14 
    15 doUsage() {
    16   cat <<_EOF_
    17 Usage: ${myname} <src_dir> <dst_dir> <base> <inc> [sed_re]
    18     Renumbers all patches found in 'src_dir', starting at 'base', with an
    19     increment of 'inc', and puts the renumbered patches in 'dst_dir'.
    20     Leading digits are replaced with the new indexes, and a subsequent '_'
    21     is replaced with a '-'.
    22     If 'sed_re' is given, it is interpreted as a valid sed expression, and
    23     is be applied to the patch name.
    24     If the environment variable FAKE is set to 'y', then nothing gets done,
    25     the command to run is only be printed, and not executed (so you can
    26     check beforehand).
    27     'dst_dir' must not yet exist.
    28     Eg.:
    29       patch-renumber.sh patches/gcc/4.2.3 patches/gcc/4.2.4 100 10
    30       patch-renumber.sh /some/dir/my-patches patches/gcc/4.3.1 100 10 's/(all[_-])*(gcc[-_])*//;'
    31 _EOF_
    32 }
    33 
    34 [ $# -lt 4 -o $# -gt 5 ] && { doUsage; exit 1; }
    35 
    36 src="${1}"
    37 dst="${2}"
    38 cpt="${3}"
    39 inc="${4}"
    40 sed_re="${5}"
    41 if [ ! -d "${src}" ]; then
    42     printf "%s: '%s': not a directory\n" "${myname}" "${src}"
    43     exit 1
    44 fi
    45 if [ -d "${dst}" ]; then
    46     printf "%s: '%s': directory already exists\n" "${myname}" "${dst}"
    47     exit 1
    48 fi
    49 
    50 Q=
    51 if [ -n "${FAKE}" ]; then
    52     printf "%s: won't do anything: FAKE='%s'\n" "${myname}" "${FAKE}"
    53     Q="echo"
    54 fi
    55 
    56 ${Q} mkdir -pv "${dst}"
    57 for p in "${src}/"*.patch*; do
    58     [ -e "${p}" ] || { echo "No such file '${p}'"; exit 1; }
    59     newname="$(printf "%03d-%s"                                     \
    60                       "${cpt}"                                      \
    61                       "$( basename "${p}"                           \
    62                           |"${sed}" -r -e 's/^[[:digit:]]+[-_]//'   \
    63                                        -e "${sed_re}"               \
    64                         )"                                          \
    65               )"
    66     ${Q} cp -v "${p}" "${dst}/${newname}"
    67     cpt=$((cpt+inc))
    68 done