In message <op.xteg74d5izronj@bluey>
WPB <wpb.feed@gmx.com> wrote:
> On Sun, 01 Feb 2015 18:08:25 -0000, Duncan Moore <duncan.moore@gmx.com>
> wrote:
>
> >
> > On 01/02/2015 13:02, WPB wrote:
> >> On Sun, 01 Feb 2015 09:38:56 -0000, Duncan Moore <duncan.moore@gmx.com>
> >> wrote:
> >>
> >>> On 31/01/2015 16:31, WPB wrote:
> >>>> CC = g++ FC = g++ PC = g++ CXX = g++So the command should at least
> >>>> produce a different error to "File -c not found". But the result of
> >>>> make was exactly the same as before.
> >>> The -c is coming from the shell. Try this:
> >>>
> >>> *set UnixEnv$.SHELLFLAGS cccc
> >>> *make
> >>> printf "Making dir...\n"
> >>> File 'cccc' not found
> >>> Makefile:2: recipe for target 'dir' failed
> >>> make: *** [dir] Error 1
> >>>
> >>> Duncan
> >>>
> >> Very interesting, Duncan, thank you. Unfortunately, that doesn't work
> >> for
> >> me:
> >>
> >> *set UnixEnv$.SHELLFLAGS cccc
> >> *make
> >> echo "Making dir...\n"
> >> File '-c' not found
> >> make: *** [dir] Error 1
> >> *show UnixEnv$.*
> >> UnixEnv$.SHELLFLAGS : cccc
> >>
> >> Could it be that you are using a different version of make?
> >>
> >
> > Yes, I have my own version of make. I'm using 4.0. I assume you're using
> > 3.81. I've just looked at the manuals and it looks like .SHELLFLAGS was
> > introduced somewhere in between. Of course, using SHELLFLAGS won't sort
> > out your problems. All it does is show that (probably) the -c is coming
> > from the shell.
> >
> > Duncan
>
> Thanks for confirming, Duncan. I am indeed using 3.81, from the GCCSDK AB.
>
> As Ron suggested before, if I could set .SHELLFLAGS to nothing, wouldn't
> that solve my problem?
>
> Anyway, I've downloaded your port of 'make' and although I've not tried it
> yet, I've read the manual and it sounds spot on. I think it's going to
> make (haha) everything much easier. I'll report back once I've tried it
> out. Many thanks!
>
> WPB
For versions of make that dont read .SHELLFLAGS, it could be worth
trying a RISC OS side alias like
Set Alias$-c %%
This seems to let (from a taskwindow)
-c show
work without the 'File '-c' not found' error, and should only affect the
CLI which isn't interested in the -c switch.
Regarding the : problem in make, there are (make) path wrappers absolute
or realpath which could be worth trying to see if it shields the path
from the normal : detection.
Duncan's make may be doing everything required, just mentioning these
possibilities while on the subject.
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
No comments:
Post a Comment