scripts: always create lib32 and lib64 symlinks

Unconditionally create the lib32 -> lib/ and lib64 -> lib/ symlinks.

This is reportedly a fix to build a toolchain for a 32-bit target on
a 'pure' 64-bit host (eg. on Fedora FC12, host libs are in lib64/,
and there is no lib -> lib64 symlink, as we can see on other distors,
as Debian). As gcc only puts static host lib in lib64/ (along with
target files in subdirs), we can safely create the symlinks.

Also note that the symlinks are summarily removed at the end
of the build.

Signed-off-by: Anthony Foiani <anthony.foiani@gmail.com>
[Yann E. MORIN: fix a comment, rephrase the commit log]
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>

diff -durN gcc-4.3.2.orig/libgcc/config/sh/t-linux gcc-4.3.2/libgcc/config/sh/t-linux

--- gcc-4.3.2.orig/libgcc/config/sh/t-linux	2009-03-07 11:42:38.000000000 +0100

+++ gcc-4.3.2/libgcc/config/sh/t-linux	2009-03-07 11:03:39.000000000 +0100

@@ -15,7 +15,7 @@

 	-Wl,--soname=@shlib_base_name@.so.1 \

 	-Wl,--version-script=@shlib_map_file@ \

 	-o @multilib_dir@/@shlib_base_name@.so.1.tmp @multilib_flags@ \

-	@shlib_objs@ -lc && \

+	@shlib_objs@ && \

 	rm -f @multilib_dir@/@shlib_base_name@.so && \

 	if [ -f @multilib_dir@/@shlib_base_name@.so.1 ]; then \

 	  mv -f @multilib_dir@/@shlib_base_name@.so.1 \