Hi, On armel architecture, the symbol differences have usually been inlined softfloat symbols being exported. Which is additional symbols and would thus not break symbol checking (if I understood correctly). What is more worrying is the lack of unofficial arch information in mole. Thus maintainers are not aware of issues with their packages on unofficial archs until someeon files a bug.
I can also see that this potentially much bigger problem for hurd/kfreebsd. > Though it's worth asking ourselves if it would make sense to have an > intermediary fallback between debian/*.symbols.<arch> and > debian/*.symbols that would be debian/*.symbols.<kernel>. One option would be to use dpkg-architecture provided variables: DEB_HOST_ARCH=armel DEB_HOST_ARCH_OS=linux DEB_HOST_ARCH_CPU=arm DEB_HOST_GNU_CPU=arm DEB_HOST_GNU_SYSTEM=linux-gnueabi DEB_HOST_GNU_TYPE=arm-linux-gnueabi Thus one can use DEB_HOST_ARCH for symbol files specific for one arch, DEB_HOST_ARCH_OS for kfreebsd/hurd DEB_HOST_ARCH_CPU when same set of symbols affects arm and armel or all > Because of a bug in libtool. I fail to see why we should be more lax > just because libtool has bugs. I think the pessimism to libtool comes from bugs like #347650 not getting solved over time.. mind you that bug would help with the same goal symbols file is working on - making transitions easier. For the c++ and -version-script bug, #430971 I think this might be much easier to fix. > That is not a correct solution. If you are able to list private > symbols, better not export them instead of flagging them. > Yes, but that's not something I control. In fact, if that's what you > want, it's better to fail so that we can report problems to maintainers who > will then prod upstream to implement a version script or similar. for most libraries, creating a version script should be be the same amount of work as separating private/public symbols in .symbols file. Also automatically generating .symbols file from version script should not be very hard. The big benefit of using version-scripts is that it makes dynamic linking much more faster, when the symbol tables have only the needed symbols. -- "rm -rf" only sounds scary if you don't have backups
signature.asc
Description: Digital signature
