On 03/02/2015 16:11, Duncan Moore wrote:
The problem is with 'make'.
This code is in job.c:
#elif defined (__riscos__)
char default_shell[] = ;
int batch_mode_shell = 0;
#else
It's not just in the RISC OS version, but in the GNU make version itself.
If I remove this code (so default_shell
In message 5550c668.2070...@gmx.com
Duncan Moore duncan.mo...@gmx.com wrote:
On 03/02/2015 16:11, Duncan Moore wrote:
The problem is with 'make'.
This code is in job.c:
#elif defined (__riscos__)
char default_shell[] = ;
int batch_mode_shell = 0;
#else
It's not
On 03/02/2015 22:00, WPB wrote:
On Tue, 03 Feb 2015 16:11:23 -, Duncan Mooreduncan.mo...@gmx.com
wrote:
On 31/01/2015 16:15, Duncan Moore wrote:
The problem is with 'make'.
This code is in job.c:
#elif defined (__riscos__)
char default_shell[] = ;
int batch_mode_shell = 0;
#else
On 02/02/2015 13:26, Theo Markettos wrote:
On Mon, Feb 02, 2015 at 11:29:24AM +, Duncan Moore wrote:
Yes, I think it is a bug. This page describes how to report bugs:
http://www.riscos.info/index.php/Bug_Reporting
Reporting the bug doesn't always mean there is someone at the other end to
On Tue, 03 Feb 2015 16:11:23 -, Duncan Moore duncan.mo...@gmx.com
wrote:
On 31/01/2015 16:15, Duncan Moore wrote:
On 31/01/2015 13:11, Duncan Moore wrote:
As to why \n is causing problems, I'm not sure. It looks like some
weird
interaction between 'make' and 'printf'.
I'm wondering
On 31/01/2015 16:15, Duncan Moore wrote:
On 31/01/2015 13:11, Duncan Moore wrote:
As to why \n is causing problems, I'm not sure. It looks like some weird
interaction between 'make' and 'printf'.
I'm wondering if it's due to 'make' calling exec() and then the argument
list being manipulated.
In message 54d0f32b.40...@gmx.com
Duncan Moore duncan.mo...@gmx.com wrote:
On 31/01/2015 16:15, Duncan Moore wrote:
On 31/01/2015 13:11, Duncan Moore wrote:
As to why \n is causing problems, I'm not sure. It looks like some weird
interaction between 'make' and 'printf'.
I'm
On 02/02/2015 14:21, Ron 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 \
Are you sure the error is in the printf binary?
in the string and results in 'File
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
*make
printf
On Sun, 01 Feb 2015 12:01:34 -, Ron b...@woosh.co.nz wrote:
The dash error for this is better -as long as it still does it when
being called from make.
$ printfMaking dir...\n
/ADFS::Trav.$/home/bin/sh: 8: printfMaking dir...\n: not found
put a space after printf and all is well.
$
In message 54ccff8d.90...@gmx.com
Duncan Moore duncan.mo...@gmx.com wrote:
On 31/01/2015 13:11, Duncan Moore wrote:
As to why \n is causing problems, I'm not sure. It looks like some weird
interaction between 'make' and 'printf'.
I'm wondering if it's due to 'make' calling
On Sun, 01 Feb 2015 09:38:56 -, Duncan Moore duncan.mo...@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
On 01/02/2015 13:02, WPB wrote:
On Sun, 01 Feb 2015 09:38:56 -, Duncan Moore duncan.mo...@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
On 31/01/2015 13:11, Duncan Moore wrote:
As to why \n is causing problems, I'm not sure. It looks like some weird
interaction between 'make' and 'printf'.
I'm wondering if it's due to 'make' calling exec() and then the argument
list being manipulated. I seem to recall that it quotes both
On Sat, 31 Jan 2015 14:49:14 -, Lee Noar leen...@sky.com wrote:
On 31/01/15 13:52, WPB wrote:
[snip]
Actually printf is on the run path already. And from the command line,
the printf command works just fine. The error File '-c' not found only
occurs when the command is executed my make.
On 30/01/2015 14:13, WPB wrote:
With this very simple test case of a Makefile:
dir :
printf Making dir...\n
mkdir OBJECTS
You need the executable file 'printf' in your run path - check that it is.
The trouble then is with the \n. I could get it to work by just removing
On Sat, 31 Jan 2015 13:11:00 -, Duncan Moore duncan.mo...@gmx.com
wrote:
On 30/01/2015 14:13, WPB wrote:
With this very simple test case of a Makefile:
dir :
printf Making dir...\n
mkdir OBJECTS
You need the executable file 'printf' in your run path - check that
In message op.xtbugtqyizronj@bluey
WPB wpb.f...@gmx.com wrote:
On Sat, 31 Jan 2015 06:51:55 -, Ron b...@woosh.co.nz wrote:
In message cb70628e54.b...@ron1954.woosh.co.nz
Ron b...@woosh.co.nz wrote:
I'm pretty sure the -c thing is because your Makefile SHELL
On 30/01/15 14:13, WPB wrote:
Actually, though, it's happy creating the dir, as long as I comment out
the printf. So it seems to be the printf which is causing the error to be
generated.
I didn't know you could use printf in the makefile.
I've used echo to output our position in the
On Sat, 31 Jan 2015 06:51:55 -, Ron b...@woosh.co.nz wrote:
In message cb70628e54.b...@ron1954.woosh.co.nz
Ron b...@woosh.co.nz wrote:
I'm pretty sure the -c thing is because your Makefile SHELL variable
is resolving to something that doesn't understand the -c switch.
I think
On Sat, 31 Jan 2015 11:09:45 -, Mitch Crawford
mi...@sand-hill.freeserve.co.uk wrote:
[snip]
I didn't know you could use printf in the makefile.
I've used echo to output our position in the past.
Both work on the RISC OS command line, as a printf binary is a standard
part of the
In message op.xtaremqgizronj@bluey
WPB wpb.f...@gmx.com wrote:
On Fri, 30 Jan 2015 20:12:22 -, Lee Noar leen...@sky.com wrote:
On 30/01/15 14:13, WPB wrote:
Hello all,
I'm running into trouble using 'make'.
With this very simple test case of a Makefile:
dir :
Hello all,
I'm running into trouble using 'make'.
With this very simple test case of a Makefile:
dir :
printf Making dir...\n
mkdir OBJECTS
(Note that 'dir :' isn't really indented.)
I get the error File '-c' not found when I invoke 'make', and the dir
'OBJECTS' is not
23 matches
Mail list logo
