On Tue, Jun 28, 2011 at 07:40:03AM +0200, Hendrik Sattler wrote: > Am Montag, 27. Juni 2011, 16:20:23 schrieb Steve Langasek: > > So this: > > > So it should be a matter of changing that to print this instead on Debian > > > multiarch: $ gcc -print-multi-os-directory > > > x86_64-linux-gnu > > > $ gcc -print-multi-os-directory -m32 > > > i486-linux-gnu
> > would definitely be wrong, because neither > > /usr/lib/x86_64-linux-gnu/x86_64-linux-gnu nor > > /usr/lib/x86_64-linux-gnu/i486-linux-gnu will exist. Correct would be '.' > > and '../i486-linux-gnu', but that's of little help if one doesn't know what > > it's relative to in the first place! > Then make it "../x86_64-linux-gnu" instead of "." > That will always work for all subdirectories of /usr/lib, no? That doesn't tell the consumer of this information what it's relative *to*. How does the consumer know that it's relative to "some subdirectory of /usr/lib", rather than relative to /usr/lib itself? (Answer: it can't.) > One question, though: > How are build tools like CMake converted to use Multiarch directories for > the installation rule? I don't have a generic recipe for converting cmake to install to the multiarch directory. If someone has one, please add it to <http://wiki.debian.org/Multiarch/Implementation>. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110628093414.gg23...@virgil.dodds.net
