Re: [gccsdk] make: File '-c' not found

In message <e682aa8f54.beeb@ron1954.woosh.co.nz>
Ron <beeb@woosh.co.nz> wrote:

> I've been able to replicate this now by putting the coreutils printf in
> the path for the CLI to find.
> Firstly, there is an error in the printf binary where it objects to a \
> in the string and results in 'File '-c' not found'.
> It is not crucial to, but by using (RISC OS)
> set alias$-c ""
> The error reporting is then more helpful:
> File name 'printf \' not recognised
> The key thing is that it can't handle a '\' at all in the string.
>
> Back to using dash and it's builtin printf, and though it works, it has
> a quirk but is workable.
>
> SHELL = dash
> dir :
> printf %b "Making dir...\\n"
> mkdir OBJECTS
>
> The format b tells it to resolve escape characters, and \\n is needed
> also.
>

I've just read
info coreutils printf invocation
on the linux pc, and all of the examples use printf 'data/text' rather
than "data/text"
This syntax works for both the coreutils and dash versions, however both
versions require the \\n to get a newline.

I dont need a %b for the dash builtin today for some reason, sometimes
these errors leave the taskwindow or other corrupted I think, and you
can get odd things until starting fresh again.

Is it possible that using the "data/txt" syntax is not only wrong but
causing corruption?

Ron M.

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
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