Your message dated Wed, 11 Aug 2010 21:54:13 +0200
with message-id <20100811195413.gb15...@rivendell>
and subject line Re: Bug#590563: dpkg-gensymbols can't handle biarch libs with
different symbol names
has caused the Debian Bug report #590563,
regarding dpkg-gensymbols can't handle biarch libs with different symbol names
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
590563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
A C++ library like libstdc++ built for 32bit and 64bit in the same source can
have different symbol names in the 32bit and 64bit builds, and different symbol
names on different architectures. The current `arch' attribute only allows
selection of the architecture.
dpkg should allow the biarch architecture names in the `arch' attribute and do
the right thing when processing libs, e.g. arch=i386 should trigger for a symbol
in a 32bit library for a build on amd64.
--- End Message ---
--- Begin Message ---
On Thu, 29 Jul 2010, Guillem Jover wrote:
> On Wed, 2010-07-28 at 23:15:33 +0200, Matthias Klose wrote:
> > just the remaining question: which are the architecture names for
> > ppc64, mips-newabi and mips64? I see that I can "invent" my own
> > ones, but I would prefer to use ones which are probably already used
> > in other places.
>
> ppc64 is a know architecture to dpkg, but it does not know about
> mips-newabi nor mips64.
Thanks. Matthias, I'm closing the bug now.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer ◈ [Flattr=20693]
Follow my Debian News ▶ http://RaphaelHertzog.com (English)
▶ http://RaphaelHertzog.fr (Français)
--- End Message ---
