[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: VMS port
From: |
hb |
Subject: |
Re: VMS port |
Date: |
Mon, 25 Nov 2013 23:28:38 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 |
On 11/25/2013 01:44 PM, Pavel Fedin wrote:
> I know, this is what i'm going to do. Actually, i want to fix output-sync
> for spawn()-based flavor. This includes EMX, DOS and potentially Cygwin.
> Currently output-sync option will not work in that ports, because the related
> fragment:
> --- cut ---
> /* Divert child output if output_sync in use. */
> if (child->output.syncout)
> {
> if (child->output.out >= 0)
> outfd = child->output.out;
> if (child->output.err >= 0)
> errfd = child->output.err;
> }
> --- cut ---
> is for some reason under #else branch only (where fork() is used). I think
> that the best way to fix this is to move this fragment out of #ifdef's. But
> above there's one more #ifdef VMS fragment, which also seems to ignore
> child->output settings. I see that VMS version of 'child_execute_job' gets
> the complete 'child' structure, i have checked it but it seems to ignore
> these new members.
> So i've got one more question - may be this fragment should become
> completely generic ? Just with some note that VMS code should also implement
> handling for it.
The VMS port does not support parallel execution of recipes. So the
output-sync (although accepted) is ignored.