[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#211092: [mlang@debian.org: Re: mklibs and brltty]



Information from the mailinglist:
----- Forwarded message from Mario Lang <mlang@debian.org> -----

To: debian-boot@lists.debian.org
Subject: Re: mklibs and brltty
In-Reply-To: <[🔎] 20030907191446.GA6249@wavehammer.waldi.eu.org> (Bastian
 Blank's message of "Sun, 7 Sep 2003 21:14:46 +0200")
From: Mario Lang <mlang@debian.org>
Date: Tue, 23 Sep 2003 15:31:20 +0200
List-Id: <debian-boot.lists.debian.org>
Resent-Date: Thu, 25 Sep 2003 12:10:00 -0500 (CDT)

Bastian Blank <waldi@debian.org> writes:

> On Sun, Sep 07, 2003 at 09:04:39PM +0200, Petter Reinholdtsen wrote:
>> Could weak symbols solve the problem?  I'm not very familiar with
>> shared library internals, but I believe a weak symbol will be selected
>> from the library if no other matching symbol is available.  If the
>> library provides such symbol, it would make mklibs happy, while the
>> shared library linker would still select the symbol from the
>> executable.  Is this correct?  I am mostly guessing based on the
>> rumors I've heard about weak symbols.

Hmm, can you give me a hint on how one is supposed to
define a weak symbol?  This is all rather new to me.

> dropping subdirs which aren't referenced via rpath from the resolver in
> mklibs. none of that libs will be reduced.

I am sorry, I do not grasp this sentence in the given context.
The problem is not reduction, at least not AFAICS.  mklibs is not
supposed to reduce /lib/brltty/lib*.so.  It only checks that
all referenced symbols are actually defined somewhere (in a library),
which fails since the missing symbol is actually defined in
the executable that loads the lib.

-- 
CYa,
  Mario | Debian Developer <URL:http://debian.org/>
        | Get my public key via finger mlang@db.debian.org
        | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44


-- 
To UNSUBSCRIBE [snip]
----- End forwarded message -----



Reply to: