Re: Specify how undefined weak symbol should be resolved in executable

["H.J. Lu" <hjl.tools@gmail.com>]

On Tue, Feb 23, 2016 at 8:49 AM, Michael Matz <matz@suse.de> wrote:
> Hi,
>
> On Tue, 23 Feb 2016, H.J. Lu wrote:
>
>> Not only we need to change defined weak symbol behavior, we also need to
>> change undefined non-weak symbol behavior when taking its address.
>
> Why?  An undefined non-weak symbol reference leads to a linker error,
> done.  Why change that?
>

Make it "external non-weak symbol", which is a symbol defined in
a shared object.



-- 
H.J.