Bonjour, > > The same error occurs on alpha, m68k, sh4 and sparc64. > > > > libseccomp-dev is available on hppa but not on the other arches. lxc build > > successfully on hppa if I include the libseccomp-dev > > dependency. Wasn't able to fix symbol issue. > > I am not sure about how I can make the symbols file vary for > architectures. I'll ask to other developers. > > If you have recommendations I'm eager to take them! :)
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! For hppa, as described by Dave Anglin above, libseccomp-dev is actually available and changing the dependency from libseccomp-dev [!alpha !hppa !m68k !sh4 !sparc64] to libseccomp-dev [!alpha !m68k !sh4 !sparc64] should allow the build to succeed there. Merci! Tom [1]: https://manpages.debian.org/unstable/dpkg-dev/dpkg-gensymbols.1.en.html
rules.diff
Description: Binary data
symbols.diff
Description: Binary data
liblxc1.symbols.sparc64
Description: Binary data
