[Oneiric, Natty, Maverick, Lucid SRU] Link libbfd statically

Stefan Bader stefan.bader at canonical.com
Tue Aug 16 18:22:32 UTC 2011


On 16.08.2011 17:58, Ben Hutchings wrote:
> On Tue, Aug 16, 2011 at 04:49:35PM +0200, Stefan Bader wrote:
>> On 14.08.2011 18:16, Ben Hutchings wrote:
>>> On Tue, 2011-08-02 at 11:38 +0200, Stefan Bader wrote:
> [...]
>>>> Actually, having said this, maybe the better solution is to modify
>>>> the build dependencies to cause the compile to have
>>>> HAVE_CPLUS_DEMANGLE set. That way we do not need to carry a
>>>> modification to the makefile which likely breaks...
>>>
>>> You *must* set HAVE_CPLUS_DEMANGLE; see Debian bug #606050.
>>>
>>> Ben.
>>>
>>>
>> Ah ok. Well I saw that setting that option preventing any linkage against
>> libbfd. Which was what the proposed patch caused by accidentally breaking all
>> the compile time tests.
>> What I was not sure of was whether using libiberty only instead of libbfd has
>> any functional drawback. But if there are actually license problems involved[1],
>> then there does not seem to be a way around only using libiberty.
>  
> AFAIK, perf only needs a C++ symbol demangling function from one
> or other of these libraries, and either version works just as well as
> the other.
> 
Ah, ok.

>> So the change would be like attached for Oneiric. The milage for other releases
>> will vary. The only thing that makes me wonder whether this correct is that ldd
>> on the resulting binary shows no reference to libiberty.
> [...]
> 
> I'm not sure about Ubuntu but in Debian binutils-dev only provides a
> static libiberty.
>
Gah, not seeing the obvious... So does ours...

> Ben.
> 





More information about the kernel-team mailing list