tags 558964 + confirmed thanks Dear Peter,
Thank you for notifying us of this. On Mon, Nov 30, 2009 at 07:32:45PM +0100, Peter Fritzsche wrote: > I build all packages some time ago with binutils-gold and your package build > without an hard failure, but I noticed that you seems to provide a library in > a specific library package so other packages can link against it without > problems.... but your shared object has still some unresolved symbols which > the program which links agaomst it must resolve. This isnt a good idea because > when you introduce new dependencies the package previously linked against the > old version will break because it doesnt know about the new dependency. > Maybe you could link against all needed libraries so programs must not link > against libraries which it doesnt need to use. I agree. > More informations can be found at > > http://wiki.debian.org/qa.debian.org/FTBFS#A2009-11-02Packagesfailingbecausebinutils-gold.2BAC8-indirectlinking > dpkg-shlibdeps already showed you the related warnings: [snip] > You've propably linked it with gcc instead of g++. This was happening. However, even after switching to g++, I get several of those warnings. Is there a way I could find out which libraries actually provide those symbols, so that I could just add them to the list of libraries to which I link? Could you suggest of a way I could do this? Attached is a build log with more details which you could parse better than myself. I can provide the patch which makes it build this way, if you desire. Thanks. Kumar -- Kumar Appaiah
speech-tools_1.2.96~beta-6_amd64.build.gz
Description: Binary data
signature.asc
Description: Digital signature
