multilib

[Peter O'Gorman]

Hi,
I'm not really too knowledgable of the problem space. What are the problems 
with multilib? Is it just that libtool searches the wrong libdirs? 
/usr/lib64 should come before /usr/lib? If that is the case, then surely it 
can be fixed fairly simply by changing our reliance on 'gcc 
-print-search-dirs' to something else (as gcc -print-search-dirs currently 
tells lies in the multilib case).

For example, I have the following script (no code comments please, this is 
just messing about):
$ cat testscript.sh
#! /bin/sh
: ${CC=gcc}
echo "int main(){return 0;}" > conftest.c
args=`$CC -v conftest.c -o conftest 2>&1`
rm -f conftest conftest.c
mylist=
for arg in $args
do
case $arg in
-L*) realdir=`echo $arg |sed -e 's/^-L//'`
realdir="`cd $realdir && pwd`"
case " $mylist " in
*" $realdir "*) ;;
*) mylist="$mylist $realdir";;
esac
;;
esac
done
echo $mylist

And when I run it (on a sourceforge FC3 compile farm host):
$ sh ./testscript.sh
/usr/lib/gcc/x86_64-redhat-linux/3.4.2 /usr/lib64
$ env CC='gcc -m32' sh ./testscript.sh
/usr/lib/gcc/x86_64-redhat-linux/3.4.2/32 
/usr/lib/gcc/x86_64-redhat-linux/3.4.2 /usr/lib /lib

Couldn't we simply replace occurences of 'gcc -print-search-dirs' with some 
code like the above in libtool.m4 to get a more reasonable value for 
sys_lib_search_path_spec. As I said, I have not got a true understanding of 
the problem. So please help me to understand it more :)

Peter
--
Peter O'Gorman - http://www.pogma.com