It is ok to have undefined hidden symbols in a .o file

[Ulrich Drepper]

"H . J . Lu" <hjl@valinux.com> writes:

> Where there are
> 
> 1. foo is undefined, hidden in bar.o
> 2. foo is defined in foo.o.

Yep, this must be possible.

> both
> 
> # gcc -shared -o libfoo.so bar.o foo.o
> # gcc -shared -o libfoo.so foo.o bar.o
> 
> should work. This patch fixes it. I'd like to check it in if it
> is ok with everyone.

Makes sense to me.

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------