> Od: Neil Williams <codeh...@debian.org> > You need to work out which library (libfoo.so) contains the undefined > references and ensure that the objects are linked against them.
I've tried. Is there some good way how find library with these referencies? > It could be that a dependency that exists outside the pbuilder chroot > changes the way that the package builds, leading to parts of the code > being enabled (or disabled) when it does not happen that way outside > the chroot. Some packages use "auto-detection" of some libraries and > these can be a source of such problems. If the package *had* built, you > could have found that the package built inside the chroot would > actually behave differently to the one built outside. Not good. Is there way to avoid this "auto-detection"? regards mira -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org