Alex Waugh alex at alexwaugh.com
Mon Jan 10 13:11:32 PST 2005


The __RISCOSIFY_STRICT_UNIX_SPECS option to riscosify is useful when
dealing with ambiguous relative filenames, however it also gets used
when dealing with filenames starting with a path variable. For example,
when it is enabled the filename Choices:Crypto.PuTTY.sshknownhosts gets
converted to Choices:Crypto/PuTTY/sshknownhosts which is not ideal. Can
anyone think of a situation when applying __RISCOSIFY_STRICT_UNIX_SPECS
to a filename starting with a path variable would be useful? If not,
I'll change it so it only gets applied to relative filenames.


Alex Waugh                                           alex at alexwaugh.com

PHP, Roots, Subversion, WebJames and more from http://www.alexwaugh.com/

More information about the gcc mailing list