undefined symbols in shared libraries

[Nick Clifton]

Hi Robert,

> There appears to have been a change in behavior w.r.t. using -z
> defs. At some point using -z defs caused the linker to exit with an
> error if there were unresolved symbols in a shared library. We
> recently upgraded to a new linker (needed the weak symbol handling
> fix for performance reasons) and now we only get warnings when using
> -z defs. I also tried --no-undefined just in case the long option
> behaves differently, but it doesn't. I further tried the combination
> of --no-undefined and --error-unresolved-symbols and that still
> didn't help.

Please try using:

  --no-allow-shlib-undefined

Cheers
        Nick