Matt Kraai <[EMAIL PROTECTED]> writes: > On Thu, Sep 04, 2003 at 03:50:53PM +0200, Mario Lang wrote: >> Now, the question is what would be the proper fix for this problem. >> >> I do see several: >> >> 1. Work around this problem by patching mklibs such that it >> detects that a certain symbol is provided by an executable. > > This is the correct solution. Executables should be able to > provide symbols that are undefined by the libraries they link > against.
I am only wondering, how would mklibs know that somelib.so is loaded by this-and-that(1)? The reverse is clear, the executable lists the libraries it requires. But how would I know that a certain lib is going to be loaded by a certain executable? -- CYa, Mario | Debian Developer <URL:http://debian.org/> | Get my public key via finger [EMAIL PROTECTED] | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
