[Debian-med-packaging] Different symbols files on different architectures

[Julien Yann Dutheil]

Dear Andreas,

I agree with your solution. The original idea of adding symbol files was to
detect interface changes between releases. Appart from very rare
exceptions, interface break on one architecture should also lead to
interface break on others, so that should be enough to have the symbols for
amd64 only.
I have pushed libbpp-qt 2.4.0, but did not add the symbol file yet. If you
show me your solution for one lib, I can propagate it to others.

All the best,

Julien.

On Fri, Apr 6, 2018 at 10:10 PM, Andreas Tille <tille at debian.org> wrote:

> Hi Julien,
>
> you see, that symbols files is a complex topic (which is why I stayed
> away usually from it).  I'm not sure whether it is worth the effort to
> maintain it for all architectures for libbpp-* since I think the only
> practival use is amd64.  If you are motivated to dive a bit deeper into
> it with the given hints that's fine for me.  I personally would go
> with my suggested solution to have symbols file only for amd64 and
> just remove it before building other architectures.  I'm fine with
> implementing this in case you agree with me.
>
> Kind regards
>
>        Andreas.
>
> On Fri, Apr 06, 2018 at 06:09:31PM +0200, Sebastiaan Couwenberg wrote:
> > On 04/06/2018 05:48 PM, Andreas Tille wrote:
> > > 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.)
> >
> > Since it's a C++ library, I suggest pkgkde-tools:
> >
> >  http://pkg-kde.alioth.debian.org/symbolfiles.html
> >
> > Or just not bother with symbols and use `dh_makeshlibs -V`.
> >
> > Kind Regards,
> >
> > Bas
> >
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20180407/3a017d1b/attachment.html>