[pkg-lxc-devel] Bug#922545: Bug#922545: lxc: FTBFS on hppa -

[Mathias Gibbens]

Control: tags -1 +pending -moreinfo

Hi Tom,

On Mon, 1 Aug 2022 15:20:02 +0200 "Tom Turelinckx" <tom at turelinckx.be>
wrote:
> Architecture-specific symbols files can be supplied by naming them
liblxc1.symbols.<arch>, for example liblxc1.symbols.sparc64. The
attached liblxc1.symbols.sparc64 was created by copying liblxc1.symbols
and then applying the attached symbols.diff. I think the same file
could be used for liblxc1.symbols.alpha, liblxc1.symbols.m68k,
liblxc1.symbols.sh4 and liblxc1.symbols.sparc64. I have verified that
building lxc 4.0.11-1 against sid on sparc64 succeeds when the attached
liblxc1.symbols.sparc64 is included in the debian directory.
> 
> Another approach could be to lower DPKG_GENSYMBOLS_CHECK_LEVEL to 0
on architectures where libseccomp-dev is not available. This will still
log the symbol differences but without failing the build. This can be
achieved by applying the attached rules.diff against debian/rules. This
approach avoids having to maintain architecture-specific symbols files.
I have verified that building lxc 4.0.11-1 against sid on sparc64
succeeds with the attached rules.diff applied.
> 
> Both approaches are documented at [1].
> 
> Could you please consider adopting either one of these approaches?
Thanks!

  Thank you for providing those examples! I think the cleanest and most
easily maintained approach would be to modify d/rules to make a symbol
difference non-fatal for those architectures we know are missing
libseccomp. Having to maintain multiple different .symbol files for
specific architectures seems error prone to me, and since the only
difference should be the lack of libseccomp-related symbols, I think
that's OK.

  I have a commit staged locally, but don't want to push it up to
master without seeking input from others.

Mathias

> [1]:
https://manpages.debian.org/unstable/dpkg-dev/dpkg-gensymbols.1.en.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-lxc-devel/attachments/20220805/c6a2c875/attachment.sig>