.la file parsing too simple for cross compiling

[Michael Taht]

We generate one set of libraries for use on both the cross compile 
target and host system(s).
for example, mips libs go in:

/opt/hardhat/devkit/mips/fp_le/target/usr/lib

The problem arises when we have (for example) a libglib.la file in that 
subdir, you get a
libdir=/usr/lib/ line in that file. This works fine for doing native 
development later - but for cross development it forces link lines such as:

/bin/sh ./libtool --mode=link mips_fp_le-gcc  -O2  -o libIDL.la -rpath 
/opt/hardhat/devkit/mips/fp_le/target/usr/lib -version-info 
4:4:4                         -release 0.6 parser.lo lexer.lo ns.lo 
util.lo  -L/opt/hardhat/devkit/mips/fp_le/target/usr/lib -lglib

to be transformed into:

mips_fp_le-gcc -shared  parser.lo lexer.lo ns.lo util.lo  
-L/opt/hardhat/devkit/mips/fp_le/target/usr/lib /usr/lib/libglib.so  
-Wl,-soname -Wl,libIDL-0.6.so.0 -o .libs/libIDL-0.6.so.0.4.4

which tries to link /usr/lib/libglib.so into the cross compile target.

Is there a way to suppress the -l expansion? Or could a future version 
of libtool use some sort of prefix variable in declaring libdir in the 
.la files? Or some other solution?