[gccsdk] Shared library soname and symlink target inconsistency

[Peter Naulls]

John-Mark Bell wrote:
> I've been playing around with cross compiling shared libraries and have
> concluded that filename handling is completely inconsistent, almost to
> the point of uselessness.
> 
> If the library's soname is not in Unix format (i.e. libfoo.so.N), then
> any binary linked to it fails to find it at load time. This is contrary
> to what !SharedLibs.docs.!ReadMe says (namely that sonames should be in
> RISC OS format), though my testing indicates that RISC OS format sonames
> simply don't work, anyway.

I haven't seen this, but that you have doesn't overly surprise me.
There is some riscosify logic in there that I added, but it may not
be comprehensive.  I certainly agree that the output of the
toolchain should be immediately usable on RISC OS.

For the sake of clarity, can you give me some exact examples so
I can make sure I can repeat this?

Thanks.