http://www.riscos.info/bugzilla3/show_bug.cgi?id=181
Summary: symlinks should use RISC OS native paths only
Product: GCC/GCCSDK
Version: other
Platform: Other
OS/Version: RISC OS
Status: NEW
Severity: feature request
Priority: P1
Component: binutils
AssignedTo: [email protected]
ReportedBy: [email protected]
Estimated Hours: 0.0
This is a sub part of a more general problem about shared library paths:
http://www.riscos.info/pipermail/gcc/2010-January/005123.html
Symlinks in RISC OS are not part of the OS (to date), but are supported by
various 3rd party modules and UnixLib. They have a 1c8 filetype, or ,1c8 when
generated in a unix environment. They are a distinct file, like a .lnk file
in Windows, rather than being a special kind of file as they are in Linux.
The rationale for the assertion is mainly that such 3rd implementations or RISC
OS itself might be expected to deal with symlinks, and not have the UnixLib
riscoify handling. This has a number of implications, some of which may
already be true:
arm-unknown-riscos-ln both cross and natively should output only links with
RISC OS format filenames.
The cross version in practice probably will only take in Unix format, as part
of package generation. Note that for cross-installed libraries intended for
cross development, the native 'ln' would still be used.
The native version perhaps could take in both, leaving riscosify to resolve
ambiguity. Or it could deal entirely in native paths.
UnixLib should understand when indirecting a symlink that it only contains a
native path, and for the symlink() function, only create native paths.
SOManager, which as a module does not have the full benefit of the UnixLib code
should understand these symlinks to contain RISC OS paths. In practice, this
probably means no change. Its handling of sonames is related, but a different
bug, and not mentioned here.
--
Configure bugmail: http://www.riscos.info/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
_______________________________________________
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
