Re: Multiarch in Debian unstable
On 2011-06-28 10:34:14 +0100, Steve Langasek wrote:
> 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.)
By reading the documentation?
Print the path to OS libraries for the selected multilib, relative
to some lib subdirectory. If OS libraries are present in the lib
subdirectory and no multilibs are used, this is usually just ., if
OS libraries are present in lib<suffix> sibling directories this
prints e.g. ../lib64, ../lib or ../lib32, or if OS libraries are
present in lib/<subdir> subdirectories it prints e.g. amd64, sparcv9
(though I don't know why it says "lib subdirectory" instead of
"lib directory" here).
Vincent Lefèvre <email@example.com> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)