> > The problem is that the linker suddenly changed behaviour and no longer
> > provided the symbols which used to satisfy those unresolved symbols. I have
> > convinced the linker to once again provide those symbols hence fixing the
> > build.
>
> I think you need to do some more testing and (re-)read the email from Geoff
> Wing which hinted at the problem. Nothing in librumpnet is creating a
> link_set_domain section and therefore the linker (2.16 or 2.19.1) doesn't
> create {__start,__stop}_link_set_domain symbols.
You failed to quote the line from the previous email where I already
stated this was not the issue. The symbols are not supposed to come
from librumpnet, but rather e.g. librumpnet_sockin and that is where
the new binutils behaviour was creating damage. Feel free to use nm on
e.g. librumpnet_sockin before and after my change from last night.
But if you refuse to understand the problem, fine. Just revert your
misguided changes.
