10/04/2019 15:45, Bruce Richardson:
> Weak functions don't work well with static library builds as the linker
> always picks the first version of a function irrespective of whether it is
> weak or not. The solution to this is to use the "whole-archive" flag when
> linking, but this has the nasty si
On Mon, May 27, 2019 at 04:57:15PM -0400, Aaron Conole wrote:
> Bruce Richardson writes:
>
> > On Mon, May 27, 2019 at 04:13:53PM +0200, David Marchand wrote:
> >>Hello,
> >>On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
> >><[1]bruce.richard...@intel.com> wrote:
> >>
> >> Wea
Bruce Richardson writes:
> On Mon, May 27, 2019 at 04:13:53PM +0200, David Marchand wrote:
>>Hello,
>>On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
>><[1]bruce.richard...@intel.com> wrote:
>>
>> Weak functions don't work well with static library builds as the
>> linker
>
On Mon, May 27, 2019 at 04:13:53PM +0200, David Marchand wrote:
>Hello,
>On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
><[1]bruce.richard...@intel.com> wrote:
>
> Weak functions don't work well with static library builds as the
> linker
> always picks the first versio
Hello,
On Wed, Apr 10, 2019 at 3:45 PM Bruce Richardson
wrote:
> Weak functions don't work well with static library builds as the linker
> always picks the first version of a function irrespective of whether it is
> weak or not. The solution to this is to use the "whole-archive" flag when
> link
Weak functions don't work well with static library builds as the linker
always picks the first version of a function irrespective of whether it is
weak or not. The solution to this is to use the "whole-archive" flag when
linking, but this has the nasty side-effect that it causes the resulting
binar
6 matches
Mail list logo