cc/gcc: remove 'sub-level' version form symbols

Now we use defconfig files to store the samples, we have to be a bit more
conservatives in the symbols names, so as to avoid gigantic version bumps
when updating sub-level versions from a package.

For example (using fictitious versions):
- in crosstool-NG 1.17.0, we choose:
- latest gcc is gcc-linaro-4.7-2012.10, which is the default for the
choice in the menuconfig
- gcc-linaro-4.6-2012.10 is selected
- so, sample has an explicit symbol for the selected gcc version, as it
is not the default
- we update to crosstool-NG 1.18.0:
- latest gcc version is gcc-linaro-4.7-2013.01
- gcc-linaro-46 has been updated to gcc-linaro-4.6-2013.01
- as the sample now has no *valid* symbol to set the gcc version, the
default is used, while we would have expected to still use the 4.6
release from linaro, not the 4.7

Get rid of sub-level (ie. the third digit sequence in versions) from the
symbols for linaro versions.

Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

 #!@@CT_bash@@

 # What we need:

 #  - the .config file

 # Parse the tools' paths configuration

 . "${CT_LIB_DIR}/paths.sh"

 # We'll need the stdout later, save it

 exec 9>&1

 # Parse the common functions

 . "${CT_LIB_DIR}/scripts/functions"

 # Don't care about any log file

 exec >/dev/null

 rm -f "${tmp_log_file}"

 # Parse the configuration file

 . .config.2

 # Parse architecture and kernel specific functions

 . "${CT_LIB_DIR}/scripts/build/arch/${CT_ARCH}.sh"

 . "${CT_LIB_DIR}/scripts/build/kernel/${CT_KERNEL}.sh"

 # Build CT_TARGET

 CT_DoBuildTargetTuple

 # All this for this single echo... :-( Sigh, I'll have to re-arrange things...

 echo "${CT_TARGET}" >&9