Hi Stefan! On 12/10/2015 05:35 PM, Stefan Ahlers wrote: > my NMU was unsuccessful and I would be really happy if you could help me.
Sure, I'm happy to help. > The problem is that there are symbols, which are different on 32bit and > 64bit based architectures. And so I'm looking for a way to handle this > in one single file instead of one file per architectures. > > In the man page of dpgk-gensymbols, I found a option called > (arch-bits=32) and (arch-bits=64) but it looks like > > (arch-bits=32)_ZThn8_N8Echonest11CatalogSongD0Ev@Base 2.1.0 > (arch-bits=64)_ZThn16_N8Echonest11CatalogSongD0Ev@Base 2.1.0 > > does not work. What's wrong? Is there any better solution? That's interesting. I haven't heard of arch-bits= before but according to the manpage of dpkg-gensymbols, it's also a very new feature supported since dpkg_1.18.0 and according to the logs, the buildds are actually using 1.18.3 in their chroots. However, outside the chroots, the installed version of dpkg is most likely 1.17.26 which is the version found in stable (since the buildds are running stable in most cases). I will need to test arch-bits= to figure out under which circumstances it fails. It might be the case that dpkg-gensymbols is actually called outside the chroot which means it's going to be the stable version instead of the unstable version of dpkg which understands arch-bits=. I will try sbuilding your package on a build host running stable and on one running unstable, however both in an unstable chroot and see if that makes a difference. In any case, the common method that I have been using so far was to use a common symbols file but specify the architecture list with "arch=amd64 arm64" and so on. This has been supported for a long time already and works with all currently deployed versions of dpkg. Cheers, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
