Le mardi 20 novembre 2007 à 16:22 +0100, Raphael Hertzog a écrit : > 2/ Watch out if adding support of symbols files break unofficial > architectures (like armel or kfreebsd-i386/amd64). Because the > pre-generated files only take into account the current list of official > architectures, so you might not be aware of some differences in the symbol > set. You can check the build log of your package on unofficial > architectures on http://experimental.debian.net/ > (http://experimental.debian.net/build.php?pkg=glibc for example). > > Feel free to make suggestions to avoid such breakage when possible. See > also discussions in http://bugs.debian.org/452022 on that topic.
A guaranteed way to trigger such issues is to export all functions built in the library as symbols, which is unfortunately the default behavior. This way the list will change if you change the optimization parameters or on unofficial architectures. If upstream doesn't support this, the simplest way to restrict the list of functions is to use a version script ; this script can be written manually or automatically generated by libtool with the -export-symbols or -export-symbols-regex options. -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `- our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
