Re: Bug#533642: dpkg-dev: dpkg-shlibdeps fails on symbols exported by libgcc_s

[Raphael Hertzog <hertzog@debian.org>]

clone 533642 -1
reassign -1 libgcc1 1:4.4.0-7
retitle -1 Ensure __aeabi_* symbols are listed in libgcc1.symbols for armel
severity -1 important
thanks

On Sat, 20 Jun 2009, Raphael Hertzog wrote:
> I think that to properly resolve my issue I have to allow you to export
> those blacklisted symbols in the libgcc1.symbols file. I'll cook up
> something to that effect but it will require a newer dpkg where symbols
> can be individually tagged with special instructions.

This is now done in git's dpkg. The feature will be in dpkg-dev 1.15.3
once it hits unstable (no estimated date yet).

You have to make sure that all __aeabi_* symbols on armel appear in the
symbols files generated for libgcc1. Since the symbols are blacklisted by
default you have to add a supplementary tag to force their inclusion.

Example:

libgcc_s.so.1 libgcc1 #MINVER#
 [...]
 (ignore-blacklist|arch=armel)__aeabi_fcmplt@GCC_3.5 1:4.4.0
 (ignore-blacklist|arch=armel)__aeabi_dcmpge@GCC_3.5 1:4.4.0
 [...]

(if you want to fix that issue sooner, you'll have to hack debian/rules to
manually add the relevant lines since dpkg-gensymbols will not be able to
do it for you)

Cheers,
-- 
Raphaël Hertzog

Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny :
http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/