El dg 24 de 02 del 2008 a les 11:22 +0100, en/na Loïc Minier va escriure: > Ok, but why not using usr/lib/$(DEB_HOST_GNU_TYPE)?
There's no package using usr/lib/i486-linux-gnu or usr/lib/x86_64-linux-gnu. Those paths are even incorrect, compilation on amd64 would need overriding DEB_HOST_GNU_TYPE. And I won't use ../lib32. > Your ld.so should > find the libs and the modules should be found by pango. What's > preventing you to use the multiarch pathnames or why are you insisting > on using /usr/lib32 / the biarch pathnames? /usr/lib32 works, it's tested. It's standard. It's the one currently used by Debian; either this or /emul/ia32-linux/usr/lib. On the other hand, what's preventing the use of DEB_BUILD_OPTIONS=arch32bit? What packages are using usr/lib/$(DEB_HOST_GNU_TYPE)? > Why is it needed? (What's the rpath pointing to and why is it > problematic?) The rpath points to /usr/lib32. That shouldn't be a problem, but lintian complains because rpath is deprecated in Debian. Perhaps you already know this: http://wiki.debian.org/RpathIssue