Re: Different symbols files on different architectures
Hi Bas,
On Fri, Apr 06, 2018 at 02:18:03PM +0200, Sebastiaan Couwenberg wrote:
> On 04/06/2018 02:08 PM, Andreas Tille wrote:
> > after adding a symbols file to libbpp-core all other architectures are
> > failing due to different symbols (see below for ppc64el[1]) but others
> > are failing as well. What is the correct way to fix this?
>
> Use (arch=ppc64el) tags for the symbols, or something more generic like
> arch-bits or arch-endian if those symbols differ based on 32/64 bits
> CPUs or big/little endian.
>
> See: dpkg-symbols(1)
> https://manpages.debian.org/unstable/dpkg-dev/dpkg-gensymbols.1.en.html#Standard_symbol_tags
I've checked this and I think I understand the task in principle but
in practice for libbpp-core that's a no-go for manual adaption to
edit about 1000 entries (may be per architecture). Is there some
tool that helps here? If not my proposed solution would be to
provide a symbols file for amd64 only and move it out of the way
in debian/rules for other architectures.
(I gave it a very minimal shot in branch symbols_i386 but gave up
after some 20+x entries.)
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: