This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: A proposed patch for undefined_symbol ()
- To: "H . J . Lu" <hjl at valinux dot com>
- Subject: Re: A proposed patch for undefined_symbol ()
- From: Koundinya K <knk at dde dot dk>
- Date: Wed, 01 Mar 2000 13:23:06 -0700
- CC: binutils at sourceware dot cygnus dot com
- Organization: DDE
- References: <20000301095946.A8291@valinux.com>
Hi hjl,
Normally when -Bsymbolic is uses when building a shared object (library) , the
linker should bind references to global symbols to their definitions within the
object, if defintions are available. Normally, since references to global
symbols within shared objects are not bound until run time, even if
definitions are available, so that definitions of the same symbol in an
executable or other shared objects can
override the object's own definition. The linker should issue warnings for
undefined symbols unless there is an option in the Linker to force a fatal error if
any undefined symbols remain at
the end of the link. So I feel we need to have a separate option in the Linker to
address this.
Thanks.
koundinya
> When we add -Bsymbolic to build a shared library, an undefined symbol
> isn't always a fatal error. This patch tries to address it. Is that ok
> to install?
>
> Thanks.
>
> --
> H.J. Lu (hjl@gnu.org)
> --
> 2000-03-01 H.J. Lu <hjl@gnu.org>