Hi Picca (2011.07.29_10:11:47_+0200) > Is there a link somewhere explaining by examples how to deal with thoses > MISSING symbols > or differences of implementations ? > > Is there a sort of concatenator script, which take all the build log and > generate a unique symbol file > with arch tags ?
It's not *that* hard to do by hand, and you mostly only have to do it once. Don't know how helpful this is, but: I've only maintained symbols for one C++ library, for a short time (they can't maintain an ABI or do releases, so I dropped the shared library, and moved it to experimental) I found that factoring out 32bit vs 64bit differences and size_t differences was all that was necessary [0]. Jakub Wilk also did some documentation of the differences between common sizes [1] [0]: http://anonscm.debian.org/loggerhead/collab-maint/re2/trunk/files/55/debian/ [1]: https://bitbucket.org/jwilk/debian-misc/src/1021f41766e3/type-mangling/ -- Stefano Rivera http://tumbleweed.org.za/ H: +27 21 465 6908 C: +27 72 419 8559 UCT: x3127 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
