Test for glib and icd use incorrect include paths for LSB builds

When building Qt 4.7.0 with the linux-lsb-g++ mkspec, the test for glib support uses the system include path instead of the LSB include path. The test should use /opt/lsb/include/glib-2.0 but instead uses /usr/include/glib-2.0 and /usr/lib64/include/glib-2.0 and this leads to the wrong decision being made regarding whether or not glib should be supported.

The test for ICD also uses some incorrect system paths instead of LSB-compliant ones (you can see that I've added my own -I/opt/lsb/include/glib-2.0 to the configure command to get past the glib problem above):

ICD auto-detection... ()
lsbc++ -c -pipe -DQT_SHARED -O2 -Wall -W -I../../../mkspecs/linux-lsb-g++ -I. -I/opt/lsb/include/glib-2.0 -I/usr/include/QtNetwork -I/usr/include/QtCore -o icd.o icd.cpp
warning: dangerous include path /usr/include/QtNetwork
warning: dangerous include path /usr/include/QtCore

It is questionable whether the QtCore and QtNetwork paths should be there at all, since a build of Qt which requires Qt to already be built would seem inconsistent.