[OE-core] boost fails to build on MIPS

[Mike Looijmans]

On current OE master, boost fails to build, because something attempts 
to add "-m32" to the gcc commandline for no apparent reason.

Can anyone confirm this, or am I the only MIPS user in the world?

For example:

| gcc.compile.c++ 
bin.v2/libs/atomic/build/gcc-4.3.1/release/threading-multi/lockpool.o
| mipsel-oe-linux-g++: error: unrecognized command line option '-m32'
|
|     "mipsel-oe-linux-g++" "-mel" "-mabi=32" "-mhard-float" 
"-march=mips32" "-Wl,-O1" "-Wl,--as-needed" 
"--sysroot=/home/milo/work/openpli-next/build/tmp/sysroots/vuduo2" 
-ftemplate-depth-128  -Os -pipe -g -feliminate-unused-debug-types 
-fvisibility-inlines-hidden -O3 -finline-functions -Wno-inline -Wall 
-pthread -fPIC -m32  -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 
-DBOOST_ATOMIC_SOURCE -DNDEBUG  -I"." -c -o 
"bin.v2/libs/atomic/build/gcc-4.3.1/release/threading-multi/lockpool.o" 
"libs/atomic/src/lockpool.cpp"

-- 
Mike Looijmans