* commands.c, function.c, hash.c, job.c, main.c, output.c:
use MAKE exit codes.
* makeint.h: encode make exit codes so that they are VMS compatible.
* job.c: check child exit code for VMS style exit codes.
* vmsjobs.c: save and return VMS style exit code.
---
commands.c |2 +-
function.c |
* job.c: split the command line at a newline.
* default.c, vmsjobs.c: change ECHO variable to a pseudo builtin, which
ensures that the VMS/DCL ECHO ("write sys$output") is used and is
correctly quoted.
* vmsjobs.c: remove unused builtin 'rm'.
---
default.c |2 +-
job.c | 22 +
* default.c, main.c, makeint.h, vmsfunctions.c: prefix argv[0] with
"mcr " for MAKE/MAKE_COMMAND and set the program name
to the image filename (without the .exe;version)
* vmsfunctions.c: remove obsolete code
---
default.c |3 +-
main.c | 14 +++--
makeint.h |8 ++-
Hi Reinier,
> > Yes, but it's an idiomatic one, oft suggested; "Unpack and run
> > `./configure && make all check install'".
>
> I don't get it. What is wrong with
>
> make -sj clean; make -sj all; make -sj check; make -sj install
That doesn't do the same thing; `make all check install' st
On Sun Aug 24 12:33:41 2014, ra...@inputplus.co.uk (Ralph Corderoy) wrote:
> Hi Paul,
>
> > > It seems a design flaw that I must
> > >
> > > make -sj clean && make -sj all && make -sj check &&
> > > make -sj install
> >
> > Well, that's because you're only considering this use-case,
>
>
