To a large degree this issue is made moot by multiarch. The rpath location is now the same as the runtime location (at least if it gets the architecture right).
We still don't want those rpaths, but a) libtool is less likely to try and put them in if it notices that built-time and runtime locations match and b) they will now point to the right place. I haven't yet noticed the override in dpkg-cross autoconf cache actually breaking anything: # override libtool until #367115 is fixed hostarch=dpkg-architecture -qDEB_HOST_GNU_TYPE lt_cv_sys_lib_dlsearch_path_spec="/usr/$hostarch/lib /lib /usr/lib /usr/local/lib" but it is wrong for multiarch and it would be good to get rid of it. I'm not sure to what degree we think this is still useful for old-style builds. In general I'd just like to fix upstream (libtool, or the package in question) and remove bodgery like this. I'll try and find out if there are cases where it interferes with multiarch crossbuilds or is still needed for dpkg-cross cross-builds. If anyone else already knows that info would be welcome. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
