Minor issue with current gcc-4.7 from experimental (x32)

[Daniel Schepler <dschepler@gmail.com>]

Greetings,
With gcc-4.7 4.7.2-18 from experimental installed on x32 (or actually
4.7.2-18+x32 which is identical except for the version and setting the
distribution to debian-ports' "unreleased"), it seems "gcc
-print-multi-os-directory" isn't printing the expected output:

root@frobozz:~# gcc -print-multi-os-directory
../libx32
root@frobozz:~# gcc -m32 -print-multi-os-directory
../lib32
root@frobozz:~# gcc -m64 -print-multi-os-directory
../lib64
root@frobozz:~# gcc -mx32 -print-multi-os-directory
../libx32

This, in turn, is causing builds of binutils to get an extraneous file
/usr/libx32/libiberty.a.  That would be a cosmetic issue, except that
binutils-m68hc1x, mingw32-binutils, etc. are also getting the file, so
it's causing file conflicts when I try to install those in my x32
buildd chroot.

This is a regression since 4.7.2-12 where the x32 build printed
"../lib" on "gcc -print-multi-os-directory", and I didn't immediately
see anything in the 4.7.2-19 changelog that would address this.  So I
just wanted to let you know about this.
-- 
Daniel Schepler