I have a utility that builds relocatable images. In order to get round problems introduced by TI's subsection mechnanism (section:subsection), I have to use a linker command file with a SECTIONS directive to combine all possible subsections created by the compiler: E.g.,
SECTIONS
{
.bss: { *(.bss) }
}
Ideally, I would like to find a better way of doing this, but it works (until a new magic section is invented). The problem is that the linker insists on objecting if the inputs do not contain any of the named sections. As an aside, it would be helpful if the message actually included the name of the section that couldn't be matched; my users do not have access to the linker command file to see what's at the reported line.
Can the linker be prevented from issuing this warning as, in my case, it never indicates a problem?
Is there a better way of combining subsections?
