Hi Yaroslav, On Tue, 07 May 2013, Yaroslav Halchenko wrote: > now the same "couldn't find library" message could be warning or error, > e.g. > > dpkg-shlibdeps: warning: couldn't find library libmat.so needed by > debian/matlab-psychtoolbox-3-nonfree/usr/lib/matlab/site/psychtoolbox-3/WaitSecs.mexa64 > (ELF format: 'elf64-x86-64'; RPATH: '') > dpkg-shlibdeps: error: couldn't find library libeyelink_core-1.9.so.58 needed > by > debian/matlab-psychtoolbox-3-nonfree/usr/lib/matlab/site/psychtoolbox-3/Eyelink.mexa64 > (ELF format: 'elf64-x86-64'; RPATH: '')
The difference between both is that libmat.so is not versioned while libeyelink_core-1.9.so.58 is versioned. The former can't have a shlibs file while the latter can have one (thus a warning in one case and an error in the other). > and in case of the error the whole run of dpkg-shlibdeps fails without > generating substvars. The situation persists even if I use documented: > > --ignore-missing-info > Do not fail if dependency information can't be found for a shared > library. Usage of this option > is discouraged, all libraries should provide dependency information > (either with shlibs files, > or with symbols files) even if they are not yet used by other > packages. > > which from the description sounds precisely what I need, but in the code is > not > influencing decision to exit with error upon $error_count. It does what it says. But it needs to find the library to be able to know that there's no association dependency information. So fix your build depends so that those libraries are available and/or set LD_LIBRARY_PATH to help dpkg-shlibdeps find the library. Honestly, I don't see the purpose of this bug report. What do you believe can be improved? Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
