[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Multiarch and ABI support

On Sat, 24 Jul 2010, Steve Langasek wrote:
> On Mon, Jul 19, 2010 at 07:02:32PM +0100, Hector Oron wrote:
> > 2010/7/18 Steve Langasek <vorlon@debian.org>:
> > > I'm puzzled why dpkg needs a unique triplet for a port.  dpkg needs to map
> > > port names to triplets, but why does it need to do the inverse?  And if it
> > > doesn't need to map triplet->port, why would the triplet need to be unique?
> > AFAICS `dpkg' relais on -dumpmachine from `gcc'
> > scripts/Dpkg/Arch.pm:68:        my $gcc_host_gnu_type = `\${CC:-gcc}
> > -dumpmachine`;
> > Then all the magic starts...
> > How would `dpkg' can then map GCC tuplets into Debian triplets being
> > the same with different Debian architecture names?
> It wouldn't.  I don't see a compelling reason for dpkg to do this at all.
> Your quote shows that dpkg *does* do this today, which I didn't remember
> before this conversation, but that's not an explanation for *why* it does -
> as opposed to dpkg directly recording what its current architecture is.

I don't know if you're all on the same page, but the pasted snippet is
from dpkg-dev and not from dpkg, so it's used at package build time only.

dpkg does record its current architecture in the dpkg binary itself and
gives it back when you do “dpkg --print-architecture”.

Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693]

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
                      ▶ http://RaphaelHertzog.fr (Français)

Reply to: