Hello people.
objdump isn't a solution either, while it sometimes can read the
other shared library, it doesn't provide the linker search patch
which is of critical importance to get this stuff right.
Hmm...
But what for is that search path?
As far as I understand, dpkg-shlibdeps
On Fri, Jan 20, 2006 at 11:57:28AM +0300, Nikita V. Youshchenko wrote:
2) we could try to use the ldconfig cache to make to work of ldd for
ourself.
Questions: - Is this really an advantage? Or has the cache the same
problems ldd has?
Hmm. In theory, ldconfig
On Thu, Jan 19, 2006 at 12:14:35AM +0100, Frank Lichtenheld wrote:
So looks it is safe to remove any path processing from dpkg-slibdeps, and
use only objdump. If something breaks, it should be fixed elsewhere (i.e.
proper shlibs data added to packages).
If we don't use the path
On Fri, Jan 20, 2006 at 03:36:36AM -0800, Steve Langasek wrote:
On Fri, Jan 20, 2006 at 11:57:28AM +0300, Nikita V. Youshchenko wrote:
2) we could try to use the ldconfig cache to make to work of ldd for
ourself.
Questions: - Is this really an advantage? Or has the cache the same
Hi,
I'm planning to apply the latest two patches on this bug report before
the mini-freeze starts if nobody opposes. You can check the whole
discussion (it's long though), or skip it and just go to the explanation
at the end. There's the patches and a small test suite. =)
Just wanted to say thanks for everything.
If you need anything please don't hesistate to ask.
Vinson
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
6 matches
Mail list logo
