John-Mark Bell wrote:
When arm-unknown-riscos-ln is used in a native RISC OS environment, it should do whatever the rest of the toolchain does wrt paths and appropriately type the link file. Off-hand, I cannot recall what the toolchain's path behaviour is.
I think this is the main problem. The rest of the toolchain is UnixLib, and makes use of riscosify around all file operations. Because SOManager is a module, it has a special version of this code based upon the special version also used for our SCL, and handling of symlinks is therefore not part of this. As in all these cases, there's a degree of ambiguity, but do you think it would be reasonable for SOManager to just "try harder" with more combinations when looking for shared libraries? _______________________________________________ GCCSDK mailing list [email protected] Bugzilla: http://www.riscos.info/bugzilla/index.cgi List Info: http://www.riscos.info/mailman/listinfo/gcc Main Page: http://www.riscos.info/index.php/GCCSDK
