Hi, Guillem in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780489 noticed that some symbols indeed changed from unsigned long to unsigned int. It is because size_t resolves to unsigned int instead of unsigned long as before. So it is rather a toolchain change that makes size_t defined in a different way.
The funny thing is that on i386 for example, unsigned long & unsinged int is the same thing, but it still mangles differently :). I think that the right solution is to get rid of size_t from public libverbiste API (replace it with unsigned long) and shield ourselves from changes like that. I'll work on that. Now, I also built 0.1.14-2 on testing i386 and it built fine (with debuild -us -uc), but when I tried *exactly the same package* from git on testing i386 (but with git-buildpackage), it fails with symbols problem. It seems that in both cases size_t resolves to a different type! It's rather strange. Cheers, Tomasz
signature.asc
Description: Digital signature
